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/qp-regressWrote 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-regress)<a href="https://agentmods.dev/skills/chrono-meta/forge-harness/qp-regress"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/qp-regress/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-regress"><img src="https://agentmods.dev/badge/skills/chrono-meta/forge-harness/qp-regress.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.00115 | $0.00828 |
| Opus 5 | $0.00057 | $0.00414 |
| Sonnet 5 | $0.00023 | $0.00166 |
| Haiku 4.5 | $0.00012 | $0.00083 |
Grade A, and why
qp-regress 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 6d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
qp-regress — Regression (re-run unchanged → surface_reach → delta)
Input: a baseline qp/run/<ts>/ and the same qp/plan/tcs.tsv. Output: qp/regress/<ts>/.
1. Re-run unchanged
Execute the baseline's TCs with qp-run without editing them. Editing a TC to make it pass is a new run, not a regression — say so if the user asks for it.
2. surface_reach — did the batch leave the entry screen?
bash plugins/fh-qp/scripts/qp_tools.sh surface-reach qp/run/<new-ts>/evidence.tsv
| result | meaning |
|---|---|
REACHED n/n |
every TC observed a screen other than the modal (entry) one |
PARTIAL k/n |
some did — report which did not, by tc_id |
NOT_REACHED 0/n |
the whole batch sat on one screen (a login wall, a dead env). Every FAIL in that run is unmeasured, not a detection — write that sentence in the report |
UNMEASURED (rc 10) |
no evidence file / empty — not a zero |
Denominator is all TCs, including ones that never executed; write surface_reach.txt with the raw line. |
3. Per-TC delta — delta.tsv
tc_id baseline_status new_status changed note
One row per TC. changed=yes on any status change or on a same-status verdict whose closure moved from MACHINE to JUDGMENT (the check got weaker). A run where every row is changed=no may say "no regression"; a run reported only as "12 PASS both times" may not — the aggregate hides a swap.
4. Report — report.md
First 8 lines: target · engine/adapter/evidence · #mtm: state · surface_reach line · counts PASS/FAIL/BLOCKED/AMBIGUOUS new vs baseline · number of changed=yes · the sentence for NOT_REACHED if it applies · what was not measured (unexecuted TCs, dropped screenshots).
Done When
surface_reach.txtholds aREACHED|PARTIAL|NOT_REACHED|UNMEASUREDline produced by the tool · [mandatory-pass].delta.tsvhas one row per TC in the baseline · [measured] — row count equals distinct tc_ids.- A NOT_REACHED run's report contains the "FAILs are unmeasured" sentence · [measured] — grep.
- The delta's
changedcolumn reflects real behavior change, not selector drift · [judged — pairing: for eachchanged=yes, the before/after DOM snapshots are attached and a second session confirms the element moved, not the locator].
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.
- 6d ago First seen · 46 lines · 115 tokens per session scan A 97527adae225
qp-regress is a skill published in the GitHub repository chrono-meta/forge-harness (14 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 828 once invoked, about $0.0006 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
taiyi-dev
A software-development stage that implements planned tasks using test-driven development, or TDD: write a failing test, make it pass, then improve the code. It checks the task plan, dependencies, file boundaries, and required completion evidence.
taiyi-test
A project workflow skill for verifying an implementation and producing a TEST.md record. TDD means writing a failing test, implementing the change, and then making the test pass; this skill checks that process and other regression cases.
harness-validate
Use when user invokes /harness-validate or wants to check whether a harness.yaml file is valid according to the Harness Protocol v1 JSON Schema. Reports validation errors with field paths and helpful fix suggestions.
test-spec
BDD test specification generation from use case artifacts using Clark's (2018) UC2.0-to-Gherkin transformation algorithm. Transforms structured use case flows (basic flow, alternative flows, extensions) into Gherkin Feature files with Given-When-Then scenarios. Analyzes test coverage completeness against use case flow…
knowject-rag-eval
A skill for creating or reviewing evaluation cases for RAG, a system that searches stored documents before generating an answer, including the quality of its citations.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.