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 ruvnet/metaharness --skill repo-genomegit clone --depth 1 https://github.com/ruvnet/metaharnessWrote 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/ruvnet/metaharness/repo-genome)<a href="https://agentmods.dev/skills/ruvnet/metaharness/repo-genome"><img src="https://agentmods.dev/badge/skills/ruvnet/metaharness/repo-genome/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/ruvnet/metaharness/repo-genome"><img src="https://agentmods.dev/badge/skills/ruvnet/metaharness/repo-genome.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.00073 | $0.00837 |
| Opus 5 | $0.00036 | $0.00418 |
| Sonnet 5 | $0.00015 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
repo-genome 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
repo-genome
Codex skill: 7-section readiness scorecard for a local repo — the ADR-031 Bundle JSON Pattern surfaced through Codex (iter 110 → 114).
What it does
Answers a different question than analyze-repo:
- analyze-repo — "which archetype / template / agents fit this repo?"
- repo-genome — "is this repo READY for that harness, and what's the risk?"
Produces a 7-section report:
- Repo profile — type, languages, build/test commands, ci presence
- Agent topology — recommended roles (maintainer / tester / security / release)
- MCP risk model — surface + numeric risk + policy posture
- Test confidence — how strong are the test signals
- Release readiness — buildable / testable / ci-wired
- Recommended harness plan — template, archetype, hosts, agents, skills
- Scorecard — risk_score, publish_readiness, test_confidence
LOCAL-only, deterministic, never executes repo code. Same invariant as
analyze-repo (inherited via the shared inventory/profile pipeline).
| Verdict | Exit | Meaning |
|---|---|---|
ready |
0 | publish_readiness >= 0.75 && risk_score < 0.35 |
needs-work |
1 | somewhere in the middle |
blocked |
2 | risk_score >= 0.7 |
Usage from Codex
/repo-genome path=./my-repo
/repo-genome path=./my-repo bundle=true
/repo-genome path=./my-repo out=./harness-genome.json
Equivalent CLI
harness genome ./my-repo # text report
harness genome ./my-repo --json # 6-field scorecard JSON
harness genome ./my-repo --bundle # ADR-031 schema-1 envelope
harness genome ./my-repo --out harness-genome.json # write scorecard to file
Sample 6-field output (--json)
{
"repo_type": "rust_node_polyglot_mcp_ci",
"agent_topology": ["maintainer", "tester", "security", "release"],
"risk_score": 0.31,
"mcp_surface": "local_default_deny",
"test_confidence": 0.86,
"publish_readiness": 0.78
}
When to use it
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 First seen · 87 lines · 73 tokens per session scan A f9793cb493d7
repo-genome is a skill published in the GitHub repository ruvnet/metaharness (648 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 837 once invoked, about $0.0004 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
C31-plan
Turn requirements into validated, executable plans. C31-brainstorm defines WHAT; C31-plan defines HOW — with coverage gates, wave analysis, and threat modeling.
C31-brainstorm
Brainstorming answers WHAT to build. It precedes planning, which answers HOW to build it.
C31-review
Reviews code changes using dynamically selected reviewer personas, then runs a verify-work pass: UAT walkthrough, verifier validation, and decision coverage logging. Writes memory/.planning/phases/XX-VERIFICATION.md.
C31-adopt-project
A guided workflow for researching a GitHub project and preparing a possible integration. It creates a report automatically, but waits for your confirmation before making changes.
C31-compound
Capture a recently solved problem as structured documentation so future occurrences take minutes instead of research cycles.
C31-curator
An information-curation and document-writing guide that turns research findings and judgments into deliverables for a chosen audience. It focuses on selecting relevant material, preserving sources, and organizing a clear narrative.