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 EricSanchezok/repo-seed --skill repo-governancegit clone --depth 1 https://github.com/EricSanchezok/repo-seedWrote 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/ericsanchezok/repo-seed/repo-governance)<a href="https://agentmods.dev/skills/ericsanchezok/repo-seed/repo-governance"><img src="https://agentmods.dev/badge/skills/ericsanchezok/repo-seed/repo-governance/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/ericsanchezok/repo-seed/repo-governance"><img src="https://agentmods.dev/badge/skills/ericsanchezok/repo-seed/repo-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00044 | $0.00582 |
| Opus 5 | $0.00022 | $0.00291 |
| Sonnet 5 | $0.00009 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
repo-governance 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evolving repository governance
Governance grows with the repository. Do not install every mechanism up front, and do not wait for a preventable failure before naming a new control.
Start with a read-only assessment
Run node scripts/audit-governance.mjs --json and read .repo-seed/manifest.json. The audit observes discrete repository facts only; it does not authorize changes.
- A
blockingrecommendation affects the safety boundary of the current work. Raise it before implementation. - An
advisoryrecommendation improves maturity without making the current work unsafe. Finish the requested work, then raise it in the handoff. - A suppressed recommendation was already declined or deferred against the same facts. Do not ask again until its assessment hash changes.
Authority boundary
You may autonomously inspect, audit, compare capability state, and produce a dry-run. Ask the user before you:
- enable a capability or add its files;
- install or replace a Git hook;
- change governance policy or a source of truth;
- connect an external system or change remote permissions.
Once a capability is enabled, untouched repo-seed-owned files may refresh through the normal upgrade channel. Preserve user-owned content and stop on conflicts.
Midstream capability workflow
- Name the new repository facts and the capability they make relevant.
- Check whether an existing or external mechanism already satisfies the need.
- Explain benefit, ongoing cost, files/processes added, and whether the recommendation blocks current work.
- Ask for authorization. Record
enabled,external,deferred, ordeclinedplus the assessment hash and concise reason. - Preview with a dry-run, apply only the approved capability, then run
node scripts/run-gates.mjs. - Update review instructions when the capability adds a new risk surface.
Promotion ladder
Promote knowledge to the cheapest layer that reliably prevents recurrence:
- one task-specific fact stays in its spec or plan;
- a repeated project convention becomes resident instruction or a focused skill;
- a rule that must hold without exception becomes a deterministic gate;
- a systemic escaped failure becomes a postmortem linked to the new guardrail.
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 · 52 lines · 44 tokens per session scan A 884a9c26f73f
repo-governance is a skill published in the GitHub repository EricSanchezok/repo-seed (8 stars, last pushed 16d ago), licensed MIT. It adds 44 tokens to every session and 582 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-31.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
contact-cache
Track all identified/contacted people across strategies. CSV-backed contact database with dedup by LinkedIn URL or email. Prevents duplicate outreach when running strategies on a recurring cadence.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.