Planr Browser Qa
Run practical browser-backed QA against real routes, forms, viewports, accessibility, console, and network behavior. Use for UI, authentication, session, navigation, or browser-network changes.
Install
$ agentstack add skill-openplanr-openplanr-planr-browser-qa ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-openplanr-openplanr-planr-browser-qa) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Planr Browser QA
Exercise the real browser surface directly and return useful findings from the current request and repository context.
Establish the target
Infer the routes, user journeys, runtime command, and relevant viewports from the request and repository. Ask one concise question only when the target or required credentials cannot be inferred. Never persist credentials, cookies, or session secrets.
Run focused browser checks
- Start or reuse the project's documented local runtime.
- Exercise the requested route and the shortest meaningful happy path.
- Check navigation, forms, responsive layout, keyboard access, visible focus, accessible names,
console errors, failed requests, and loading or error states that are relevant to the change.
- When a browser capability is unavailable, report the exact missing capability and provide the
smallest runnable fallback; do not invent a PASS.
- Remain report-only. When the user also wants fixes, return reproducible findings that a coding
workflow can act on, then rerun Browser QA after those changes are available.
Return
- Outcome: pass, issues-found, or blocked, with one sentence.
- Coverage: routes, journeys, viewports, and checks actually exercised.
- Findings: prioritized reproducible problems with path or UI location and expected behavior.
- Fixes: changed files and verification, or none.
- Issues: missing capability or unresolved risk, or none.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: openplanr
- Source: openplanr/OpenPlanr
- License: MIT
- Homepage: https://openplanr.dev
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.