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/pudo-testsgit 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/pudo-tests)<a href="https://agentmods.dev/instructions/dongduong2001/pudo-code-system/pudo-tests"><img src="https://agentmods.dev/badge/instructions/dongduong2001/pudo-code-system/pudo-tests.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.00210 | $0.00210 |
| Opus 5 | $0.00105 | $0.00105 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
pudo-code-system pudo-tests.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
Test Code Guidelines
Follow PUDO workflow: Plan -> Understand -> Develop -> Optimize.
Test Structure
- Match existing test patterns and conventions.
- Use descriptive test names that explain expected behavior.
- Keep tests focused on a single behavior or scenario.
Test Coverage
- Add tests for new features and bug fixes.
- Cover edge cases: empty input, boundary values, error conditions.
- Test both success and failure paths.
Test Quality
- Avoid testing implementation details.
- Prefer testing public API contracts.
- Keep tests deterministic and independent.
- Mock external dependencies, not internal code.
Verification
- Run full test suite:
npm test - Check for flaky tests
- Verify test isolation
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 · 32 lines · 210 tokens per session scan A 85ed84f55636
pudo-code-system pudo-tests.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 210 tokens to every session, about $0.0011 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.
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.
skillkit CLAUDE.md
Instructions for sacredvoid/skillkit, covering skillkit, github pages, skill file format and git remote.