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-checkgit 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-check)<a href="https://agentmods.dev/skills/ancienttwo/repo-harness/repo-harness-check"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-check/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-check"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.00385 |
| Opus 5.5 | $0.00012 | $0.00154 |
| Sonnet 5.5 | $0.00006 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
repo-harness-check 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 10d 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-check
Bot entrypoint for planning and verification decisions. Confirm the repo, scope, subject revision and worker ownership.
Mode Selection
- Create a plan only when a design decision needs it:
references/create.md. - Review an existing plan:
references/review.md. - Assess verification: consume commands, results, revision and environment. Ask the worker for missing checks from the target repo's agent instructions. Select independent review by the diff's Review by risk tier in the development flow; a low tier gets none.
- Deployment readiness:
references/deploy-readiness.md. - PR classification, and pre-merge verification of an external PR:
references/pr-verification.md. - Review-comment triage for PR follow-up:
references/review-comment-triage.md. - Architecture or refactor evidence for a scheduling decision:
references/architecture-evidence.md. repo-harness supplies the evidence; the Bot decides what to schedule.
Boundaries
Ordinary tasks do not require an Approved plan or a contract file. Reuse passing evidence only for its recorded subject. Run delta checks after edits. Report failed, stale, timed-out or omitted coverage. Missing optional tooling is a diagnostic. Use independent review for large changes, security/permissions, or unresolved uncertainty. Review does not authorize implementation or publication.
For skill-effectiveness claims, require full_test_count > 0, dry_run_ratio <= 30%, and graders reported. Mark non-authoritative: dry-run-heavy or all-dry-run evidence. Mark unavailable: no current eval evidence. Does not claim skill-effectiveness authority from dry-run benchmark output.
What ships with it
6 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.
- 10d ago Changed · +3 lines 961c2a279fa5
- 14d ago Changed · +2 lines d4b434a51c14
- 17d ago Changed · +3 lines 209da91b04e5
- 24d ago Changed · -16 lines · -6 tokens per session 8ba737252f23
- 1mo ago Changed 972688dd8f58
- 1mo ago First seen · 48 lines · 36 tokens per session scan A 963365ff6d62
repo-harness-check is a skill published in the GitHub repository Ancienttwo/repo-harness (435 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 385 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-08-30.
Other skills, from other repositories
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
validate-release-green
Run or inspect the local Release-Green observer for an exact base or combined PR candidate, separating hard failures, advisory drift and incomplete evidence. Use for maintainer preflight; full CI acceptance remains a separate requirement.
ship
Pre-release gate. Run the full gate, responsive + render checks, then produce the release checklist (README badge/current/changelog). Use before tagging a release.
verify-and-ship
Choose proportionate validation, fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
release-sidecar
Release new versions of sidecar. Covers version tagging with semver, td dependency updates, go.mod validation, CHANGELOG updates, GoReleaser automation, Homebrew tap updates, and verification steps. Use when preparing or executing a release.
ship-workflow
Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…