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/lilchris007/agents.md_generator/agents-mdgit clone --depth 1 https://github.com/Lilchris007/AGENTS.md_generatorWrote 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/lilchris007/agents.md_generator/agents-md)<a href="https://agentmods.dev/instructions/lilchris007/agents.md_generator/agents-md"><img src="https://agentmods.dev/badge/instructions/lilchris007/agents.md_generator/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 | $0.01797 | $0.01797 |
| Opus 5 | $0.00898 | $0.00898 |
| Sonnet 5 | $0.00359 | $0.00359 |
| Haiku 4.5 | $0.00180 | $0.00180 |
Grade A, and why
AGENTS.md_generator 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 4d 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
98% identical to AGENTS.md_generator AGENTS.md — 1 line 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file is for coding agents (Codex/Claude/Cursor/etc.). Keep it strict and actionable.
Overview
- Project: AGENTS.md Generator
- Stack: python (vanilla)
- Keep changes small and verifiable.
Repo context (read this first)
Project: AGENTS.md Generator
Stack: python
Repo root: .
Quick orientation
-
Start here:
README.md
-
CI workflows live in:
.github/workflows/ -
Planning/spec drafts (if used):
- Plans:
plans/ - Drafts/specs:
drafts/
- Plans:
-
Useful scripts (if any):
scripts/
Commands (copy/paste)
Lint
make lint
Format
make format
Tests
make test
Local environment notes
- Prefer the repo's existing toolchain (don't upgrade it).
- If you need new env vars: document names, don't invent secrets.
- If a command fails due to missing deps, explain the minimal install step.
Where to put new things
- Small scripts/utilities —
scripts/ - Specs/exec notes —
drafts/ - Plans (if requested) —
plans/
Guardrails (how to not break AGENTS.md Generator)
Your job: be useful, be safe, be boring. Small diffs. Deterministic output. No surprises.
0) Scope & intent
- Implement exactly what's requested. If requirements are ambiguous: ask one precise question (or make the smallest reasonable assumption and state it).
- Prefer changing existing code over adding new systems.
- Avoid framework upgrades unless explicitly asked.
1) Safe edits only
- Keep diffs small (target: <300 lines unless unavoidable).
- Never rewrite whole files when a patch will do.
- Preserve formatting, naming patterns, and local conventions.
2) No destructive operations
- Do not delete data, migrations, buckets, or user files.
- Avoid broad refactors touching many modules at once.
- Never remove features because unused without explicit instruction.
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.
- 4d ago First seen · 258 lines · 1,797 tokens per session scan A b6b83325df94
AGENTS.md_generator AGENTS.md is an instructions file published in the GitHub repository Lilchris007/AGENTS.md_generator (2 stars, last pushed yesterday), licensed MIT. It adds 1,797 tokens to every session, about $0.0090 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to AGENTS.md_generator AGENTS.md, differing in 1 line, and is treated as a copy.
Other instructions, from other repositories
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
SeekMoney-ai CLAUDE.md
Claude Code instructions for zykooooooooo/SeekMoney-ai, covering claude.md, project overview, development commands, development and production.
slivingdoc AGENTS.md
AGENTS.md instructions for baalimago/slivingdoc, covering agents.md — slivingdoc, architecture, package map, event flow and startup wiring (main.go).