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 skills add chrono-meta/forge-harness --skill qp-plangit clone --depth 1 https://github.com/chrono-meta/forge-harnessWrote 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/chrono-meta/forge-harness/qp-plan)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/qp-plan"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/qp-plan/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/qp-plan"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/qp-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 6 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.1 | $0.00131 | $0.01092 |
| Opus 5 | $0.00066 | $0.00546 |
| Sonnet 5 | $0.00026 | $0.00218 |
| Haiku 4.5 | $0.00013 | $0.00109 |
Grade A, and why
qp-plan 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 3d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qp-plan — Prepare (inventory → MECE → TCs)
Input: a target that passed qp_tools.sh target-class (PUBLIC or PROFILE_OK) and an adapter line from adapter-probe. Optional: a plan/spec document path (--plan <file>). Optional profile.
1. Surface inventory — observe, do not guess
Open the entry route with the adapter (web: navigate + accessibility snapshot; desktop: screenshot). Record every navigable surface you can see: links/routes, menu items, buttons that open a dialog, forms, tabs. One row each:
| id | kind (route·menu·dialog·form·tab) | label as shown | how reached (from which surface, which action) | observed? (yes/no) |
Rules: ⓐ do not invent routes — a surface is listed only if you saw its trigger; ⓑ parameterised routes (/item/:id) are listed as ROUTE_PARAMETERIZED, not filled with a made-up id; ⓒ if the entry route did not load → stop with HARNESS_ERROR reason=entry-unreachable. Write qp/plan/inventory.md with the header lines target-class: … (the tool's literal output), ADAPTER=… evidence=dom|pixel (the probe's literal output), engine=mcp-fallback (or engine=capability:<id> only if the qp router found a registered capability — never a browser name; a floor-tier sim wrote engine=chromium when this line did not say so, 2026-09-05), plan_doc: <path|NONE>.
2. MECE check
Walk the inventory once more against the snapshot: any visible navigable element not in the list → add it (missing); any two rows reaching the same surface → merge (overlap). Write the count of each fix under ## MECE in inventory.md. Zero fixes is a legitimate value; an unstated count is not.
3. Test-case design — qp/plan/tcs.tsv
Tab-separated, header row:
tc_id surface_id precondition step_verb step_target expected expected_source priority
step_verb∈navigate click input verify(one verb per row; a multi-step TC is several rows sharingtc_id).expected_source∈PLAN_DOC INVENTORY CODE HUMAN— where the expected value came from. With no plan document every row isINVENTORY(orHUMANif the user told you). This field is what letsqp-runlabel a finding differs from plan vs code differs; a TC without it cannot be run.preconditionis what must be true before step 1 (e.g.at:/,logged-in). Writenoneexplicitly when there is none.- At least one TC must carry a state-changing verb (
clickorinput) — a verify-only plan never exercises the runner (qp_tools.sh run-verbsenforces this on the run output). - Minimum: inventory ≥ 5 surfaces, TCs ≥ 3 for a first pass; say when the target is too small to reach that (a one-page site can be).
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.
- 3d ago First seen · 43 lines · 131 tokens per session scan A 599f27342bcf
qp-plan is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 1,092 once invoked, about $0.0007 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-09-06.
Other skills, from other repositories
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
e2e
Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".
chrome-automation
A browser-automation toolkit for controlling Chrome to visit pages, interact with forms, collect data, run tests, and create screenshots or PDFs.
playwright-automation
Browser automation and testing with Playwright. Use when testing web applications, automating browser tasks, taking screenshots, or validating UI behavior.
browser-check
Drive a real browser and come back with a MEASUREMENT rather than an impression - console errors and >=400 responses as counts, computed styles as JSON when appearance is disputed. Use when work touches UI, when a review must verify one, or when fidelity-gate asks for its measurement.
playwright
Browser automation, web scraping, E2E testing, and visual regression with Playwright. Covers 30+ patterns: login flows, form testing, responsive design checks, broken link validation, API mocking, data extraction, PDF generation, accessibility audits (axe-core), performance budgets (Lighthouse), visual diffing…