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/qcri/codebadger/agents-mdgit clone --depth 1 https://github.com/qcri/codebadgerWhat 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.00537 | $0.00537 |
| Opus 5 | $0.00269 | $0.00269 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00054 | $0.00054 |
Grade A, and why
codebadger 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.
The source is not reproduced here
Licensed GPL-3.0
The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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 · 50 lines · 537 tokens per session scan A f92affed93b2
codebadger AGENTS.md is an instructions file published in the GitHub repository qcri/codebadger (162 stars, last pushed yesterday), licensed GPL-3.0. It adds 537 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
LeAgent AGENTS.md
Instructions for vixues/LeAgent, covering leagent development guidelines, project overview, architecture, execution topology (one kernel, many ingresses) and surface map (where things live).
do-it AGENTS.md
Instructions for tdwhere123/do-it, covering agents.md, file rules, repository, source of truth vs build artifacts and closed-set contracts.
opendigitalproductfactory AGENTS.md
AGENTS.md instructions for OpenDigitalProductFactory/opendigitalproductfactory, covering dpf — agent rulebook, 1. first principles, 2. project architecture, 3. branching, commits & prs and 4. verification — build gate (mandatory).
moo-tasks AGENTS.md
Instructions for dizlexic/moo-tasks, covering agents.md, 1. what is the moo tasks board?, 2. connecting your agent, 3. available mcp tools and 4. recommended workflow for agents.
opendigitalproductfactory copilot-instructions.md
Copilot instructions for OpenDigitalProductFactory/opendigitalproductfactory: Read /AGENTS.md at the repo root before any work in this project. It is the canonical rulebook; tool-specific files in this repo are pointers to it.
opendigitalproductfactory CLAUDE.md
Claude Code instructions for OpenDigitalProductFactory/opendigitalproductfactory, a project described as: This is the official open digital product factory.