Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/instructa/planr/planr-verify-webnpx skills add instructa/planr --skill planr-verify-webgit clone --depth 1 https://github.com/instructa/planrWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/instructa/planr/planr-verify-web)<a href="https://agentmods.dev/skills/instructa/planr/planr-verify-web"><img src="https://agentmods.dev/badge/skills/instructa/planr/planr-verify-web.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00039 | $0.00975 |
| Opus 5 | $0.00019 | $0.00487 |
| Sonnet 5 | $0.00008 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
planr-verify-web scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Planr Verify Web
Prove the frozen feature runs. Planr owns the evidence contract and capability selection; the host executes the configured method. Never install or configure browser infrastructure on behalf of this skill.
Run The Typed Verification Packet
Keep verification in the coordinator. Use one stable worker identity that differs from the responsible maker. Do not spawn another model.
PLANR_WORKER_ID="coordinator-verifier-1" planr evidence verify --scope plan --id <plan-id> --json
This command leases verification, probes readiness, seals the run index, executes the configured adapter, evaluates coverage, and settles the FeatureRun. Product source is read-only. Only Planr runtime state, receipts, logs, and artifacts may change.
Require planr.execution_state.v2; its budget and absolute deadline are opaque supplied authority. Skills must not recompute budget policy. If the selected adapter cannot honor required capability or the packet is held, stop with that exact classification.
If readiness is blocked, do not choose another unregistered tool or downgrade the observation. The FeatureRun enters a capability hold. Report the returned gap and next_action, then stop. Repair the policy, schema, adapter digest, runtime registration, or permissions before you run the same verify command again.
Target Lifecycle
The configured Evidence adapter owns target startup, connection, and cleanup. Do not manually start a duplicate browser or application process unless the sealed work packet explicitly declares an externally managed target.
Run The Verification
Exercise the flow the item changed — not the homepage. Interact and assert on the required rendered output. Capture a screenshot only for a visual criterion or failure diagnostics.
Use only the repository capability selected by the active obligation. Read object.coverage, object.feature_run_verification_settlement, and object.verification_broker from the verify result. Do not issue per-criterion coverage or explain commands on the normal path. They are diagnostic commands for a known gap, and --scope criterion accepts a criterion id, never a requirement id.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 63 lines · 39 tokens per session scan A d2bb3e67a86f
planr-verify-web is a skill published in the GitHub repository instructa/planr (71 stars, last pushed 8d ago), licensed MIT. It adds 39 tokens to every session and 975 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
qa/e2e-playwright
Playwright E2E 测试完整方法论，涵盖项目初始化、Page Object Model、认证复用、API Mock、视觉回归、多浏览器测试、CI 集成和调试技巧.
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…
e2e-check
Run E2E tests or interactive browser verification. Triggers on: 'run e2e', 'e2e test', 'browser test', 'check in browser', 'verify UI', 'interactive test'.
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
ac-qa-e2e-review
Reviews spec implementation with E2E visual browser validation via Playwright. Triggers on keywords: e2e review, visual review, spec review, browser validation.
ac-qa-test-e2e
Executes E2E tests from definition files with Playwright browser automation. Triggers on keywords: test e2e, run e2e, execute e2e test, e2e test runner.