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/dongduong2001/pudo-code-system/markdown-docsgit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWhat 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.00082 | $0.00082 |
| Opus 5 | $0.00041 | $0.00041 |
| Sonnet 5 | $0.00016 | $0.00016 |
| Haiku 4.5 | $0.00008 | $0.00008 |
Grade A, and why
pudo-code-system markdown-docs.instructions.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.
What it actually says
Markdown Documentation Instructions
- Keep documentation concise and actionable.
- Match nearby heading style and table format.
- Prefer relative links for repo files.
- Verify new internal links point to existing files.
- Avoid long pasted content when a short summary and link are enough.
- Keep examples concrete and task-oriented.
- For methodology docs, distinguish required gates from optional guidance.
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 · 14 lines · 82 tokens per session scan A 6fa09077b8ad
pudo-code-system markdown-docs.instructions.md is an instructions file published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 26d ago), licensed MIT. It adds 82 tokens to every session, about $0.0004 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
arai CLAUDE.md
Instructions for taniwhaai/arai, covering claude.md — arai, commands, architecture, prompt-collector module (src/promptcollector.rs) and extending the match pipeline.
docs AGENTS.md
Instructions for argos-ci/docs, covering agents.md, always use the documentation skills and keep the table of contents in sync.
kleosrules AGENTS.md
Instructions for kleosr/kleosrules, a project described as: Cursor harness pack: user rules, skills, Bash hooks, local HANDOFF memory. macOS, Linux, Windows (WSL).
cinematic-ui AGENTS.md
Instructions for akseolabs-seo/cinematic-ui, covering agents.md, what this project is, primary goal, read order and rules for agents.
PixelPilot uiux-footer.instructions.md
Footer design, links, and site information.
agent-kit CLAUDE.md
Claude Code instructions for work0r-ai/agent-kit, covering workorai-agent-kit — agent instructions, implementation protocol, preconditions (first step), 1. prior-art search (before planning) and 2. diary (.tasks/, gitignored).