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/prompt-librarygit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWrote 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/dongduong2001/pudo-code-system/prompt-library)<a href="https://agentmods.dev/instructions/dongduong2001/pudo-code-system/prompt-library"><img src="https://agentmods.dev/badge/instructions/dongduong2001/pudo-code-system/prompt-library.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.1 | $0.00128 | $0.00128 |
| Opus 5 | $0.00064 | $0.00064 |
| Sonnet 5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
pudo-code-system prompt-library.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 5d 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
Prompt Library Instructions
- Preserve the existing prompt structure unless the task is a format migration.
- Include clear context, variables or inputs, the prompt body, and expected output.
- Add quality gates, edge cases, failure modes, or anti-patterns when the prompt changes behavior.
- Keep prompt examples realistic and scoped.
- Avoid vague success criteria such as "make it better."
- Skills should state when to use them, the workflow to follow, and the expected output.
- Do not duplicate large checklist content already maintained under
quality/.
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.
- 5d ago First seen · 14 lines · 128 tokens per session scan A 0bfdb96ac109
pudo-code-system prompt-library.instructions.md is an instructions file published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 29d ago), licensed MIT. It adds 128 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
supergraph AGENTS.md
AGENTS.md instructions for datit309/supergraph, covering supergraph — mandatory workflows, skills, auto language detection, tiered workflow — pick the right tier first and full pipeline (tier 3).
openehr-assistant-plugin AGENTS.md
Instructions for Cadasto/openehr-assistant-plugin, covering ai guidelines: openehr assistant plugin, project overview, domain context, companion mcp server and calling conventions the server enforces.
diffler AGENTS.md
Instructions for jamestkelly/diffler, covering agents.md, 1. think before coding, 2. simplicity first, 3. surgical changes and 4. goal-driven execution.
cinematic-ui CLAUDE.md
Instructions for akseolabs-seo/cinematic-ui, covering claude.md, purpose, read first, installation and cross-agent files.
cinematic-ui GEMINI.md
Instructions for akseolabs-seo/cinematic-ui, covering gemini.md, project summary, core workflow, primary platform note and repo guidance.
cinematic-ui copilot-instructions.md
Instructions for akseolabs-seo/cinematic-ui, covering repository custom instructions for github copilot, project goal, important context, if you edit workflow rules and writing style.