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-productgit 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-product)<a href="https://agentmods.dev/skills/ancienttwo/repo-harness/repo-harness-product"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-product/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-product"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-product.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.00250 |
| Opus 5.5 | $0.00012 | $0.00100 |
| Sonnet 5.5 | $0.00006 | $0.00050 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
repo-harness-product 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-product
Bot entrypoint. Confirm the product goal and source requirements.
Mode Selection
- A real new product needs a PRD:
references/prd.md. - A requested backlog needs ordering:
references/sprint.md. - A requested bounded Goal session needs preparation:
references/goal.md.
Task Authority
The GitHub issue and PR own task identity, claim, status and dependencies. Before preparing execution, read the current issue, assignees, all comments and linked PRs. Follow the repository's issue-claim rules. Planning references do not authorize work or override an active claim. Do not mint task IDs, contracts, offers or leases.
Boundaries
Use a short worker brief or PR description for ordinary tasks. Do not mark artifacts Approved on the user's behalf. Preserve existing approval. Deferred work stays in GitHub issues. Product planning does not install ChatGPT or execute backlog work. Delegate execution only within the existing authorization and named scope.
What ships with it
3 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 · +9 lines · +2 tokens per session 19a17ebcc9d1
- 24d ago Changed · -7 lines · -2 tokens per session 5bae5cdc3a76
- 1mo ago First seen · 30 lines · 30 tokens per session scan A af93f55a4470
repo-harness-product 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 250 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
agenticx-custom-project
A project guide for building applications with AgenticX, an agent-building platform, and deciding whether a bug or feature belongs in your own repository or the platform's upstream repository. It also covers drafting issues and pull requests.
project-initializer
Initializer agent for the project-level harness — turn a spec or issue into featurelist.json, init.sh, verify.yaml, and an initial commit.
project-switching
Project switching implementation in sidecar: project discovery, state management, UI flow, modal rendering, filtering, theme preview, and plugin reinitialization. Use when working on the project switcher feature, project management, worktree switching, or the project configuration system.
corp-new
A workflow for creating a new department folder inside a local agent headquarters, with its own rules, skills, tasks, and links back to the headquarters.
manager
A session-to-GitHub tracker that creates, updates, and reads issues across repositories, including their labels, parent epics, and project-board placement.
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.