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 treatmentgit 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/treatment)<a href="https://agentmods.dev/skills/ancienttwo/repo-harness/treatment"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/treatment/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/treatment"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/treatment.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 21 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00024 | $0.00428 |
| Opus 5.5 | $0.00010 | $0.00171 |
| Sonnet 5.5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
repo-harness 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.
What it actually says
Bounded frontier stress test — eval treatment
This is an evaluation-only delta over the fixture's minimum-effective-interview baseline. It has no authority to approve or implement a plan.
Eligibility
Use the treatment only when explicitly requested or when a case changes high-risk architecture, data authority or ownership, security, permissions, money, deletion, concurrency, recovery semantics, or a hard-to-reverse public interface. Bypass it for small bug fixes, decision-complete acceptance criteria, documentation, formatting, and renames.
Protocol
- Resolve environment facts from
CASE.md; do not ask the user for known facts. - Model only high-impact decisions and their prerequisites. A decision enters the current frontier only after every prerequisite is resolved.
- Emit at most three frontier questions per round. Each question includes a recommended default and the effect of every option.
- Stop after two rounds per invocation. Further expansion requires explicit
continue; unvisited branches remain explicit. - Never answer a user-owned decision. Mark it
[UNKNOWN:BLOCKING]and keep the planDraft. - Persist resolved decisions into existing authority: canonical terms to
docs/spec.md#Canonical Terms; user need/non-goal to PRD; boundary and trade-off to Plan; allowed scope and failure semantics to Plan + Contract; verifiable behavior to Contractexit_criteria; long-lived architecture to its architecture module/request. Reversible defaults use[ASSUMED]. - Shared understanding requires user confirmation. Never mark an unresolved plan Approved and never start implementation from this mode.
Hard kills
- Never create a parallel context, ADR, decision-tree, or grill-session artifact.
- Never expose the transient decision graph as durable authority.
- Never ask a downstream question in the same round as its unresolved prerequisite.
- Never trigger on a simple or decision-complete task.
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 · 44 lines · 24 tokens per session scan A bf1b99827593
repo-harness is a skill published in the GitHub repository Ancienttwo/repo-harness (434 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 428 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-05.
Other skills, from other repositories
create-modal
Create declarative modals using the modal library API. Covers modal types (confirm, input, select, form), sections (Text, Buttons, Input, Textarea, Checkbox, Select, List, Combo, When, Custom), rendering with OverlayModal, and keyboard/mouse handling. Use when adding modals or dialogs to the application.
merge-strategy
Git merge strategies, conflict resolution approaches, merge vs rebase recommendations, and branch integration patterns in sidecar. Covers pull strategy menu, direct merge workflow, squash merge, commit message templates, configurable defaults, and protected branches. Use when working on git merge features or making…
agenticx-query-data-source
Use when the user asks about verifiable quantitative facts (stock prices, financial indicators, macro data, company registry, academic metrics, legal statutes) that must come from a live data source rather than training memory.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
autoprompt
Run explicitly requested Autoprompt v2 work through the private controller. Ordinary coding and review requests do not activate this skill.
autoprompt
Run explicitly requested Autoprompt v2 work through the private controller. Ordinary coding and review requests do not activate this skill.