repo-seed: seed an agent-native, self-governing repository Agent Skill

Seed, audit, adopt, and progressively evolve an agent-native repository with risk-triggered specs, durable decisions, resident governance…

Context cost
62.3k tokensestimated from the bundle, loaded when it triggers
Bundle
90 files · 408.5 kB16 scripts among them — read before you run
Licence
MITthe author’s own terms
Last change
—v0.6.2
Servers it uses
Noneruns standalone

What it does

Seed, audit, adopt, and progressively evolve an agent-native repository with risk-triggered specs, durable decisions, resident governance skills, capability state, deterministic gates, and safe upgrades. Use when initializing or upgrading a repository, when an unmanaged repository grows complex, or when delivery, ownership, security, release, or incident signals suggest a governance capability is missing.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

agentproductivity

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md15.6 kB · preview
--- name: repo-seed license: MIT compatibility: Node >= 18; works in any repository regardless of language or framework metadata: generator: true category: scaffolding version: 0.6.2 allowed-tools: Read Write Edit Bash ---
13# repo-seed: seed an agent-native, self-governing repository
14
15repo-seed turns a traditional repository — empty or existing, any technology stack — into an agent-native repository whose governance grows with its actual risk: resident instructions, risk-triggered Specs, durable MADR decisions, incident feedback, three in-repo skills, deterministic gates, and a capability manifest that preserves user ownership and external sources of truth.
16
17**repo-seed is a progressive governance system, not a static template.** It may autonomously inspect, audit, and produce a dry-run. Writing the baseline, enabling a capability, installing a hook, changing policy/source-of-truth, or connecting an external system requires user authority. Re-running repo-seed is the only upgrade channel: untouched seeded files refresh, user-modified files are preserved, and user-created files are never deleted.
18
19In a managed repository, the resident AGENTS router is authoritative. Ordinary implementation consumes its standing rules and linked project documents directly; review, durable decisions, and governance evolution use the resident repo-review, repo-decisions, and repo-governance skills. Invoke the global repo-seed skill only for seeding, adoption, governance-layer upgrades, or upstream repair.
20
21## Workflow
22
23Run the five steps in order. Analysis, interview, and instantiation require model judgment; scaffold, record, audit, and verification mechanics are deterministic scripts.
24
25### 1. Analyze
26
27Inspect the target repository (read-only):
28
29- Stack manifests: package.json, pyproject.toml, go.mod, Cargo.toml, requirements.txt, Gemfile, etc. Detect test/lint commands plus actual unit, integration, end-to-end, fixture, and naming conventions when derivable.
30- Representative implementation: when code exists, sample two or three real entry points, modules, and public interfaces. Identify the repository's canonical domain nouns, state-transition verbs, naming idioms, and abstraction/placement conventions from repeated evidence; do not promote one outlier into policy.
31- Existing files at seeded paths (see the file list in step 4). List every conflict: a file already exists where repo-seed wants to write.
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,985 words
Files90
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈160
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
62,140
on trigger
The instruction body and 89 supporting files, read only when the skill fires.
31.1%
of a 200k window
Ten skills this size would not fit in the window together.
050k100k150k200k context window

62.3k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

It asks the agent to write files, using whatever file access your client already has. Whether it reaches the network is not declared.

What it asks for
Writes filesyes
Network accessnot declared

Read from the allowed-tools line of this skill’s own SKILL.md. It also asks for Bash, which could do either, so what is not named there is not ruled out. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

90 files, 408.5 kB on disk. Mostly text — the instructions the model reads — with 16 scripts in it that your client would run only if the instructions tell it to. 6 files of its source are not in the download — listed after these, with why.

  • SKILL.md15.6 kB
  • AGENTS.md4.8 kB
  • CLAUDE.md0.1 kB
  • CONTRIBUTING.md1.4 kB
  • LICENSE1.1 kB
  • README.md7.7 kB
  • .github/pull_request_template.md0.4 kB
  • .repo-seed/manifest.json8.6 kB
  • .repo-seed/update-strategy.md2.4 kB
  • assets/governance-map.svg4.5 kB
  • assets/seed-workflow.svg4.6 kB
  • docs/AGENTS.md3.7 kB
  • docs/ai-disclosure.md1.3 kB
  • docs/architecture.md5.0 kB
  • docs/development.md2.8 kB
  • docs/testing.md4.3 kB
  • references/decision-standard.md4.6 kB
  • references/doc-standard.md4.6 kB
  • references/interview.md6.8 kB
  • references/review-standard.md6.4 kB
  • references/update-strategy.md6.3 kB
  • scripts/audit-governance.mjs7.7 kB
  • scripts/capabilities.mjs14.8 kB
  • scripts/governance.test.mjs21.8 kB
  • scripts/governance-config.mjs3.4 kB
  • scripts/install-hooks.mjs4.5 kB
  • scripts/run-gates.mjs2.7 kB
  • scripts/scaffold.mjs39.3 kB
  • scripts/scaffold.test.mjs30.4 kB
  • scripts/verify-commit-msg.mjs2.2 kB
  • scripts/verify-decisions.mjs4.7 kB
  • scripts/verify-decisions.test.mjs4.5 kB
  • scripts/verify-doc-links.mjs6.3 kB
  • scripts/verify-manifest.mjs5.9 kB
  • scripts/verify-placeholders.mjs3.1 kB
  • scripts/verify-postmortems.mjs3.3 kB
  • scripts/verify-specs.mjs4.7 kB
  • .github/ISSUE_TEMPLATE/bug.md0.2 kB
  • .github/ISSUE_TEMPLATE/feature.md0.2 kB
  • .github/workflows/ci.yml0.7 kB
  • docs/decisions/0000-use-markdown-architectural-decision-records.md2.6 kB
  • docs/decisions/0001-repo-seed-is-a-skill-not-a-template.md3.8 kB
  • docs/decisions/0002-self-governing-repository-design.md4.6 kB
  • docs/decisions/0003-repo-review-instantiated-per-project.md4.2 kB
  • docs/decisions/0004-optional-extensions-core-minimal.md5.0 kB
  • docs/decisions/0005-readme-visual-system.md3.3 kB
  • docs/decisions/0006-readme-image-cache-safe-paths.md2.7 kB
  • docs/decisions/0007-preserve-external-source-provenance.md4.2 kB
  • docs/decisions/0008-separate-change-contracts-from-durable-decisions.md3.9 kB
  • docs/decisions/0009-progressive-capability-governance.md5.0 kB
  • docs/decisions/0010-unified-gates-and-authorized-hooks.md4.4 kB
  • docs/decisions/0011-optimize-tests-for-risk-adjusted-evidence.md3.1 kB
  • docs/decisions/0012-route-governance-through-resident-instructions.md3.0 kB
  • docs/decisions/0013-embed-human-readability-in-existing-governance.md3.7 kB
  • docs/decisions/README.md6.1 kB
  • docs/postmortems/0000-stale-readme-svg-cache.md2.3 kB
  • docs/postmortems/README.md1.6 kB
  • docs/specs/0000-progressive-ai-native-governance.md1.8 kB
  • docs/specs/0001-risk-driven-testing-policy.md2.5 kB
  • docs/specs/0002-resident-governance-skill-routing.md2.2 kB
  • docs/specs/0003-human-readable-implementation-guidance.md2.6 kB
  • docs/specs/README.md2.2 kB
  • references/templates/AGENTS.md.tpl4.4 kB
  • references/templates/CLAUDE.md.tpl0.1 kB
  • references/templates/CODE_OF_CONDUCT.md.tpl2.4 kB
  • references/templates/CODEOWNERS.tpl0.6 kB
  • references/templates/CONTRIBUTING.md.tpl1.4 kB
  • references/templates/LICENSE.tpl1.1 kB
  • references/templates/SECURITY.md.tpl0.6 kB
  • .agents/skills/repo-decisions/SKILL.md3.2 kB
  • .agents/skills/repo-governance/SKILL.md3.0 kB
  • .agents/skills/repo-review/SKILL.md7.2 kB
  • references/templates/.repo-seed/update-strategy.md.tpl2.4 kB
  • references/templates/docs/AGENTS.md.tpl3.7 kB
  • references/templates/docs/ai-disclosure.md.tpl1.3 kB
  • references/templates/docs/architecture.md.tpl1.3 kB
  • references/templates/docs/development.md.tpl2.8 kB
  • references/templates/docs/release-policy.md.tpl2.0 kB
  • references/templates/docs/testing.md.tpl4.0 kB
  • references/templates/.github/workflows/ci.yml.tpl0.7 kB
  • references/templates/docs/decisions/0000-use-markdown-architectural-decision-records.md.tpl2.8 kB
  • references/templates/docs/decisions/0001-repo-seed-is-a-skill-not-a-template.md.tpl3.9 kB
  • references/templates/docs/decisions/0002-self-governing-repository-design.md.tpl4.5 kB
  • references/templates/docs/decisions/0003-repo-review-instantiated-per-project.md.tpl3.6 kB
  • references/templates/docs/decisions/README.md.tpl4.6 kB
  • references/templates/docs/postmortems/README.md.tpl1.5 kB
  • references/templates/docs/specs/README.md.tpl2.2 kB
  • references/templates/.agents/skills/repo-decisions/SKILL.md.tpl3.3 kB
  • references/templates/.agents/skills/repo-governance/SKILL.md.tpl3.0 kB
  • references/templates/.agents/skills/repo-review/SKILL.md.tpl4.7 kB

Not in the download

Not carried is a type a skill download does not hold. Take them from its source.

  • .editorconfignot carried
  • .gitattributesnot carried
  • .gitignorenot carried
  • assets/hero.webpnot carried
  • assets/png/governance-map.pngnot carried
  • assets/png/seed-workflow.pngnot carried
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 16 scripts beside the text, so the download is 90 files — not the whole of its source: 6 files are left out. They are listed under the files, with why. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# repo-seed: seed an agent-native, self-governing repository · 62.3k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/repo-seed-seed-an-agent-native-self-governing-rep/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/repo-seed-seed-an-agent-native-self-governing-rep" ] && { [ ! -e .claude/skills/repo-seed-seed-an-agent-native-self-governing-rep ] || { mv .claude/skills/repo-seed-seed-an-agent-native-self-governing-rep "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/repo-seed-seed-an-agent-native-self-governing-rep" .claude/skills/ && echo "Installed .claude/skills/repo-seed-seed-an-agent-native-self-governing-rep"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add ericsanchezok/repo-seed-seed-an-agent-native-self-governing-rep

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/repo-seed-seed-an-agent-native-self-governing-rep/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/repo-seed-seed-an-agent-native-self-governing-rep/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/repo-seed-seed-an-agent-native-self-governing-rep" ] && { [ ! -e ~/.claude/skills/repo-seed-seed-an-agent-native-self-governing-rep ] || { mv ~/.claude/skills/repo-seed-seed-an-agent-native-self-governing-rep "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/repo-seed-seed-an-agent-native-self-governing-rep" ~/.claude/skills/ && echo "Installed ~/.claude/skills/repo-seed-seed-an-agent-native-self-governing-rep" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/repo-seed-seed-an-agent-native-self-governing-rep/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as repo-seed in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, repo-seed-seed-an-agent-native-self-governing-rep. Not in this download: 6 files of its source (the full list, and why). Take them from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Version0.6.2
Publishedno release date on file
PriceFree
Referenceericsanchezok/repo-seed-seed-an-agent-native-self-governing-rep

Versions

v0.6.2 is what is on the shelf; no release here carries a date. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

v0.6.2
  • No earlier releases have been published to the marketplace.
Pinning

The install command always fetches the release that is current the day you run it — v0.6.2 today — and cannot ask for an earlier one. The copy on your disk does not change until you run it again.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill