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 Ancienttwo/repo-harness --skill repo-harness-testgit clone --depth 1 https://github.com/Ancienttwo/repo-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/ancienttwo/repo-harness/repo-harness-test)<a href="https://agentmods.dev/skills/ancienttwo/repo-harness/repo-harness-test"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-test/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/ancienttwo/repo-harness/repo-harness-test"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-test.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00031 | $0.00189 |
| Opus 5.5 | $0.00012 | $0.00076 |
| Sonnet 5.5 | $0.00006 | $0.00038 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
repo-harness-test 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 12d 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.
What it actually says
repo-harness-test
Worker entrypoint. Confirm this is the repo-harness source checkout.
Mode Selection
- Extend tests and select real fixtures:
references/authoring.md. - Select affected tests and inspect runtime cost:
references/running.md. - Move or remove tests without losing coverage:
references/refactor-evidence.md. - Assign checks to CI lanes:
references/verification-plan.md.
Boundaries
Follow the target repo's test instructions. Preserve assertions unless behavior
changes require them. Do not fabricate pre-fix logs or acceptance results.
Report command, result, revision, environment and incomplete coverage.
Diagnosis belongs to hunt; acceptance decisions belong to the Bot.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago Changed · -9 lines · +31 tokens per session a364e70714e6
- 1mo ago First seen · 33 lines · 0 tokens per session scan A 7ca84e9f786f
repo-harness-test is a skill published in the GitHub repository Ancienttwo/repo-harness (434 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 189 once invoked, about $0.0001 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-13.
Other skills, from other repositories
feature-loop
Coding agent for the project-level harness — one feature per session, must verify, must be mergeable.
qa
Run scalable, isolated live QA for nac development. The top-level local orchestrator must parse n (default 4), dispatch one setup worker with this skill, copy its n assignment contracts verbatim into exactly n parallel test workers with this skill, then dispatch one aggregate worker with this skill using all test…
openlore-write-tests
Write and run real tests for a function or spec scenario after reading implementation and contract evidence. Use when asked to add, improve, or repair tests without stubs or placeholders.
superpowers
Use when the user wants a disciplined software development workflow with design-first planning, implementation plans, TDD, systematic debugging, code review, or verification-before-completion, adapted from obra/superpowers.
ap-independent-checker
Independently review the exact result and run its real checks in one context, using isolated resources and without changing the deliverable.
ap-execharness-resolver
Report the compatibility redirect to ap-worker; this retired role cannot perform new work.