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/coderdeltalan/agent-rules-kit/agents-mdgit clone --depth 1 https://github.com/CoderDeltaLAN/agent-rules-kitWhat 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.01112 | $0.01112 |
| Opus 5 | $0.00556 | $0.00556 |
| Sonnet 5 | $0.00222 | $0.00222 |
| Haiku 4.5 | $0.00111 | $0.00111 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- agent-rules-kit AGENTS.md — 91% identical, 3 lines differ
How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — agent-rules-kit
Scope: this file applies repository-wide to all work in this repository, unless a more specific nested AGENTS.md exists for a subtree. Authority: explicit user instructions come first, then this AGENTS.md, then repository documentation and runbooks.
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.
- 2d ago First seen · 196 lines · 1,112 tokens per session scan A aa963b143cdc
agent-rules-kit AGENTS.md is an instructions file published in the GitHub repository CoderDeltaLAN/agent-rules-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 1,112 tokens to every session, about $0.0056 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
anchor copilot-instructions.md
Instructions for peva3/anchor, covering github copilot instructions, required reading, critical rules, prohibited actions and project structure.
Harness-for-codex AGENTS.md
Instructions for ganimjeong/Harness-for-codex, covering codex harness instructions, commands, repository layout, operating principles and task loop.
anchor CLAUDE.md
Instructions for peva3/anchor: All project rules, patterns, and requirements are defined in AGENTS.md.
Harness-for-codex CLAUDE.md
Instructions for ganimjeong/Harness-for-codex, a project described as: Codex harness for consistent AI-assisted development workflows, including agent instructions, standard setup/check/test/eval scripts, CI, hooks, and documentation. | AI 기반 개발 작업을 일관되게 진행하기 위한 Codex 하네스입니다. 에이전트 지침, 표준 setup/check/test/eval 스크립트…
agents-md-doctor AGENTS.md
Instructions for ItsHege/agents-md-doctor, covering agents.md doctor public agent instructions, scope of this file, project goal, current baseline and working rules.
ai-project-template AGENTS.md
Instructions for TheSmuks/ai-project-template, covering project context, project overview, build & run, install dependencies and build.