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/genuschristellaoverhang846/agent-rules-kit/agents-mdgit clone --depth 1 https://github.com/genuschristellaoverhang846/agent-rules-kitWrote 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/genuschristellaoverhang846/agent-rules-kit/agents-md)<a href="https://agentmods.dev/instructions/genuschristellaoverhang846/agent-rules-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/genuschristellaoverhang846/agent-rules-kit/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.01064 | $0.01064 |
| Opus 5 | $0.00532 | $0.00532 |
| Sonnet 5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
agent-rules-kit 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 5d 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.
This is a copy
91% identical to agent-rules-kit AGENTS.md — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — agent-rules-kit
This file is mandatory for every AI assistant, coding agent, or chat working on this repository.
The repository must be handled with strict CDLAN discipline. Do not improvise a new workflow.
Current project
agent-rules-kit is a local Python CLI that diagnoses baseline quality of AI agent instruction files in repositories.
Core boundaries:
- Local-first.
- Read-only by default.
- No network access in runtime behavior.
- No LLM dependency in runtime behavior.
- No execution of commands from analyzed repositories.
- No security guarantees or exaggerated claims.
- Secret-like findings must be redacted.
Operating modes
There are two different work modes.
Mode 1 — Genesis / Inception
Genesis is only for creating the project from zero before remote GitHub protection exists.
During Genesis, work on main is temporarily allowed, but only under these rules:
- main must start clean before every mutation.
- Create one file at a time whenever possible.
- Before stage, the prompt/status should show exactly one untracked or modified item.
- Stage exactly one file.
- Review the staged diff visibly.
- Commit that one file.
- Return main to clean state.
- Repeat.
Genesis pattern:
- main clean.
- create one file.
- validate that file.
- status shows one change.
- stage exact file only.
- staged shows one file.
- diff staged is visible.
- no unstaged changes.
- commit.
- main clean.
Allowed exception:
- The first identity baseline may include README.md, LICENSE, and .gitignore together because they form the repository identity baseline.
Mode 2 — Always-Green
Always-Green begins only after Genesis is closed.
Genesis is closed when:
- local main is clean;
- local checks pass;
- AGENTS.md exists;
- scripts/check.sh exists and passes;
- tests exist and pass;
- CI exists or a documented reason explains why it does not yet exist;
- remote is created intentionally;
- initial push is verified;
- main protection/ruleset is applied or explicitly tracked as a blocker.
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.
- 5d ago First seen · 193 lines · 1,064 tokens per session scan A 652aa2750619
agent-rules-kit AGENTS.md is an instructions file published in the GitHub repository genuschristellaoverhang846/agent-rules-kit (1 stars, last pushed 2d ago), licensed MIT. It adds 1,064 tokens to every session, about $0.0053 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to agent-rules-kit AGENTS.md, differing in 3 lines, and is treated as a copy.
Other instructions, from other repositories
Orquestrador-Maestro AGENTS.md
AGENTS.md instructions for IAPro-Community/Orquestrador-Maestro, covering agents.md, escopo, regras de edição, arquivos gerados and publicação.
godpowers AGENTS.md
AGENTS.md instructions for hannsxpeter/godpowers, covering godpowers - agent brief, reading order, architecture, conventions and quality rules.
godpowers CLAUDE.md
Claude Code instructions for hannsxpeter/godpowers: This project uses Godpowers. See AGENTS.md for the project context.
agnt CLAUDE.md
Claude Code instructions for agnt-gg/agnt, covering claude ai instructions for agnt, project overview, local-first architecture, architecture and tech stack.
odin-sentinel AGENTS.md
AGENTS.md instructions for bradheitmann/odin-sentinel, covering odin sentinel agent instructions, role pattern, operating rules, operator ergonomics and completion report.
code-discipline-skills AGENTS.md
Instructions for eliranpv11/code-discipline-skills, covering code discipline, priority order, 1. think before coding, 2. verify reality before acting and 3. simplicity first.