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/jondoescoding/jondoescoding-coding-rules/agents-mdgit clone --depth 1 https://github.com/jondoescoding/jondoescoding-coding-rulesWhat 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.00125 | $0.00125 |
| Opus 5 | $0.00063 | $0.00063 |
| Sonnet 5 | $0.00025 | $0.00025 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
jondoescoding-coding-rules 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 yesterday.
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.
What it actually says
Agent Guide
Start at docs/index.md.
Required reading
- Architecture before changing the CLI or template destinations.
- Template standard before adding or editing rules.
- Contributing before validating or publishing changes.
Critical rules
- Keep templates source-controlled under
templates/<target>/. - Preserve target-specific formats; do not force one agent's syntax onto another.
- Keep this file lean. Put durable explanations in the linked knowledge graph.
- Never publish or push without explicit user authorization.
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.
- yesterday First seen · 17 lines · 125 tokens per session scan A e2d1c1102442
jondoescoding-coding-rules AGENTS.md is an instructions file published in the GitHub repository jondoescoding/jondoescoding-coding-rules (2 stars, last pushed 1mo ago), licensed MIT. It adds 125 tokens to every session, about $0.0006 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
agent-toolkit AGENTS.md
Instructions for sanity-io/agent-toolkit, covering sanity project, commands, mcp setup, schema & types and development.
sage CLAUDE.md
Instructions for gendigitalinc/sage, covering claude.md, project, commands, repository structure and test tiers.
agent-rules testing.instructions.md
Instructions for lirantal/agent-rules, covering testing guidelines for node.js applications, general testing principles, guiding principles, descriptive test naming (three-part structure) and structure tests by the aaa pattern.
lagune CLAUDE.md
Instructions for wellwelwel/lagune, covering sdh (security-driven hardening): lagune, 1. what this workspace is, the problem it exists to solve, what lagune actually ships and flexible by design.
fast-mcp-telegram CLAUDE.md
Claude Code instructions for leshchenko1979/fast-mcp-telegram, covering fast-mcp-telegram, session corrections and 2026-05-27.
agent-rules child-process.instructions.md
Instructions for lirantal/agent-rules, covering system processes secure coding guidelines, your mission and spawning system processes.