Borrowing it
Nothing to install: this file belongs to EricSanchezok/repo-seed. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/EricSanchezok/repo-seed/main/AGENTS.mdgit 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/instructions/ericsanchezok/repo-seed/agents-md)<a href="https://agentmods.dev/instructions/ericsanchezok/repo-seed/agents-md"><img src="https://agentmods.dev/badge/instructions/ericsanchezok/repo-seed/agents-md.svg" alt="Measured on agentmods" 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.01036 | $0.01036 |
| Opus 5 | $0.00518 | $0.00518 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
repo-seed AGENTS.md 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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
repo-seed: a cross-tool skill that seeds agent-native, self-governing repositories
Repository governance
This repository's governance layer is managed by repo-seed; product code remains repository-owned. .repo-seed/manifest.json is authoritative for managed files, capability state, governance paths, external sources of truth, and the installed repo-seed version.
Route governance work explicitly:
- Change or pull-request review must use
repo-review. - A durable choice with meaningful alternatives must use
repo-decisions. - New complexity, delivery, ownership, security, release, or incident signals must use
repo-governance. - Seeding, adoption, governance-layer upgrades, or upstream repair must use the global
repo-seedskill. If it is unavailable, stop and ask rather than hand-copying upstream governance. - Ordinary implementation follows this file and the linked project documents without invoking repo-seed again.
If automatic skill activation is unavailable, read the linked resident SKILL.md directly and follow it.
Repository layout
See docs/architecture.md for the module map and seams. Directories named there are the canonical layout; anything else is user code.
Code readability
Write code for human readers. Keep the primary logic path visible; introduce an abstraction only when it hides more complexity than its indirection adds; choose names that reveal domain meaning, effects, and cost; use one repository term per concept; and keep behavior within its owning boundary.
Commands
- Test:
node --test scripts/*.test.mjs - Lint:
npm run lint (if configured) - Gates:
node scripts/run-gates.mjs
Run relevant tests while working and the shared gate runner before every commit. CI or an installed pre-commit hook may repeat the exhaustive matrix.
Governance loop (hard rules)
- Run the gates before every commit; install the optional pre-commit capability only with user authorization.
- Record a decision in docs/decisions/ when a change chooses among meaningful alternatives whose rationale may be revisited; decisions are not a change log.
- Risk-boundary changes start from an Approved spec in docs/specs/; routine changes are exempt.
- A subtle, systemic, or costly escaped failure earns a postmortem in docs/postmortems/ linked to a permanent guardrail.
- Implementation materially derived from an external source retains provenance at the closest stable repository location; follow docs/development.md.
- The only upgrade channel for the seeded governance layer is re-running the repo-seed skill. Never hand-edit seeded files to "match upstream"; re-run the skill instead.
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.
- 8d ago First seen · 76 lines · 1,036 tokens per session scan A 1f14801601be
repo-seed AGENTS.md is an instructions file published in the GitHub repository EricSanchezok/repo-seed (8 stars, last pushed 12d ago), licensed MIT. It adds 1,036 tokens to every session, about $0.0052 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 instructions, from other repositories
data-scientist copilot-instructions.md
Repository instructions for a data-science workflow in GitHub Copilot, covering datasets, statistics, and analysis files.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.