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-architecturegit 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-architecture)<a href="https://agentmods.dev/skills/ancienttwo/repo-harness/repo-harness-architecture"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-architecture/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-architecture"><img src="https://agentmods.dev/badge/skills/ancienttwo/repo-harness/repo-harness-architecture.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.00583 |
| Opus 5 | $0.00015 | $0.00292 |
| Sonnet 5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
repo-harness-architecture 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 13d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-harness-architecture
Use this command when the harness already exists and the user wants a focused architecture documentation, drift-request, or diagram pass.
Protocol
- Confirm the target repo path and architecture scope.
- Inspect
docs/architecture/index.mdand pending files underdocs/architecture/requests/. - When the scope maps to repo code or config, resolve the capability with:
repo-harness run capability-resolver match --repo <repo> --path <path> --format json
- Update the smallest relevant architecture artifact:
- umbrella status in
docs/architecture/index.md - module or snapshot docs under
docs/architecture/ - Mermaid fenced block in the relevant module or snapshot Markdown when a visual flow materially helps
- umbrella status in
- Use Markdown Mermaid as the only architecture diagram artifact. Do not generate standalone HTML; use the external
mermaidskill only to review layout and renderability before shipping the Markdown source. - Archive handled requests with:
repo-harness run archive-architecture-request --request <request> --status <resolved|superseded|rejected|no-change> --artifact <path> --note <text>- For
resolved, the livePendingrequest must declare> **Architecture Module**:and that exact existing module path must be supplied as an--artifact.
- Verify with:
repo-harness run check-architecture-syncrepo-harness run capability-resolver validate --repo <repo> --format textrepo-harness run check-task-workflow --strictwhen repo workflow surfaces changed
Failure Modes
- If no pending architecture request exists, report
no-changeand do not invent one. - If capability resolution is ambiguous, stop at the matching paths and ask for a narrower scope.
- If
check-architecture-sync.shblocks in strict mode, resolve or archive the pending request card for the touched capability before finishing the worktree. - If diagram validation fails, fix the Mermaid Markdown source or report the validation failure; do not substitute HTML.
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.
- 13d ago First seen · 45 lines · 30 tokens per session scan A 88060e064730
repo-harness-architecture is a skill published in the GitHub repository Ancienttwo/repo-harness (431 stars, last pushed yesterday), licensed MIT. It adds 30 tokens to every session and 583 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
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-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.
openlore-execute-refactor
Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.
openlore-plan-refactor
Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.
openlore-debug
Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.
openlore-implement-story
Implement a brownfield story with OpenLore orientation, risk checks, spec validation, tests, and drift detection. Use when asked to implement or continue a story in an existing codebase.