Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/chrono-meta/forge-harnessnpx agentmods add skills/chrono-meta/forge-harness/qpWrote 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)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/qp"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/qp/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"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/qp.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.00138 | $0.01375 |
| Opus 5.5 | $0.00055 | $0.00550 |
| Sonnet 5.5 | $0.00028 | $0.00275 |
| Haiku 4.5 | $0.00014 | $0.00137 |
Grade A, and why
qp 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 1mo 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qp — Quality Platform router
One entry point for people who want to dynamically test a web or desktop app with a QA lens from inside Claude Code. Three stages, each its own skill, each leaving files:
| stage | skill | you get |
|---|---|---|
| Plan | qp-plan |
qp/plan/inventory.md (surfaces the app exposes) + qp/plan/tcs.tsv (test cases) |
| Automation (run) | qp-run |
qp/run/<ts>/verdicts.tsv + masked evidence (DOM snapshots or screenshots) |
| Regression | qp-regress |
qp/regress/<ts>/surface_reach.txt + per-TC delta vs the previous run |
Glossary (one line each, because a first-time reader asked): TC = test case · inventory = the list of screens/routes/menus the app exposes · MTM = each finding is labeled as planned / differs from the plan document / code differs · precondition = what must already be true before a step runs (logged in, page loaded), checked not assumed — a failure before it is met is BLOCKED, not FAIL · surface_reach = how many TCs actually left the entry screen · engine = which machinery drove the run (see §Engine).
Step 0 — classify the target (mechanical, never by eye)
bash plugins/fh-qp/scripts/qp_tools.sh target-class <https://… | app:NAME> [--profile <file>]
| result | rc | what you do |
|---|---|---|
PUBLIC |
0 | proceed |
PROFILE_OK |
0 | proceed with the profile |
PROFILE_REQUIRED |
4 | stop. Say: "this target is not public; QP needs a profile file — copy plugins/fh-qp/qp_profile.example.yaml to a gitignored path, fill the host/app, and re-run with --profile." Do not improvise a run against a private host. |
UNKNOWN |
10 | stop, report the target form QP accepts |
Step 1 — probe the adapter (mechanical; unknown ≠ present)
List the MCP tool names this session actually has (from your tool list — do not guess), then:
bash plugins/fh-qp/scripts/qp_tools.sh adapter-probe --need web|desktop --tools "<comma-separated tool names>"
ADAPTER=… evidence=dom|pixel → proceed and write that line into every artifact header.
HARNESS_ERROR (rc 10) → stop. Write qp/HARNESS_ERROR.txt with the reason and tell the user which MCP to connect (Playwright MCP for web · computer-use MCP for desktop). This is not a pass and not a skip.
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.
- 1mo ago First seen · 66 lines · 138 tokens per session scan A 4d8467c02c41
qp is a skill published in the GitHub repository chrono-meta/forge-harness (30 stars, last pushed yesterday), licensed MIT. It adds 138 tokens to every session and 1,375 once invoked, about $0.0006 per session on Opus 5.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
browser-qa
Drive a real headless browser against a locally-served web UI and capture screenshot evidence, reporting step-level PASS/FAIL/BLOCKED with extracted DOM text and console errors. Use when a phase on the docker QA image must exercise a rendered UI and attach screenshots — it complements the text-evidence verify/qa-test…
browser-inspect
Browser inspection and interaction for verifying rendered web UI during development.
mstar-e2e
Separately requested E2E / real-browser / device / installed-deployment verification. Load only for an explicit request or amazing-e2e-check; never from routine QA or missing screenshots.
evoflow-chat-smoke
An end-to-end check for the EvoFlow web chat: it can start or reuse a local Vite app, log in, create a conversation, send a chosen message, and check the displayed messages and reply. End-to-end testing checks a complete user flow rather than one small function.
web-ui-test
Test the IronClaw web UI using the Claude for Chrome browser extension.
nobrainer-browser
Use when the owner says nb-browser or nobrainer-browser, asks to inspect or operate a rendered website, attach to an existing approved Chrome/Edge session, restart an approved non-default Chromium profile for loopback CDP, reproduce a browser flow, run Playwright tests, or record and analyze a Playwright trace. Prefer…