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 agentmods add instructions/0xbeycan/genesis/agents-mdgit clone --depth 1 https://github.com/0xBeycan/genesisWhat 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 | $0.00543 | $0.00543 |
| Opus 5 | $0.00271 | $0.00271 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
genesis 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 3d 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.
AGENTS.md — Genesis development
Rules for working on this repo: the Genesis skeleton itself. The product
lives in templates/ — everything there ships to forks;
everything outside it is our workshop. Forked to start a project? Read
GENESIS.md first — these workshop rules are not for you.
Session protocol
- Start: read this file, then
docs/memory/(context → progress → decisions). - End: update
docs/memory/progress.md(andcontext.md/decisions.mdwhen relevant). Keep entries short.
Rules
- The repo is written in English; chat may be any language.
- The product is
templates/. Any change inside it is a product change and ships with aCHANGELOG.mdentry (version bump) — CI enforces this. - One home per rule. A rule lives in exactly one file; everything else
points to it. Product rules:
templates/AGENTS.md§3. Workshop rules: this file. Sole exception: wrappers and hooks may repeat the safety-net reminders (the always-on skill; the templates-change → CHANGELOG rule; the fork →GENESIS.mdpointer). - The version lives only in
CHANGELOG.md. - ADR threshold: open an ADR (
docs/architecture/adr/) when a live alternative was rejected or a decision would tempt a future undo; every locked decision gets a line indocs/memory/decisions.md. - No test runner here (docs-only repo, deliberate): verify guard/CI changes by running their commands locally before pushing.
- Skills: the product's skills are our skills —
.claude/skills/*symlinks intotemplates/skills/, wiring only the ones that apply to a docs-only repo (ponytail,clean-code,write-adr,ideate);ponytailis always on. The rest reference product-only process files and stay unwired here. - Commit only when asked. Never commit secrets.
NEVER
- Write placeholder syntax outside
templates/— history files (ADRs,CHANGELOG.md) may quote it; CI encodes exactly those exemptions. - Change
templates/without aCHANGELOG.mdentry. - Duplicate a rule instead of pointing at it.
- Auto-commit without being asked.
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.
- 3d ago First seen · 45 lines · 543 tokens per session scan A 6082e84b0d94
genesis AGENTS.md is an instructions file published in the GitHub repository 0xBeycan/genesis (11 stars, last pushed 1mo ago), licensed MIT. It adds 543 tokens to every session, about $0.0027 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 instructions, from other repositories
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.