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/agents-mdgit 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/agents-md)<a href="https://agentmods.dev/instructions/dongduong2001/pudo-code-system/agents-md"><img src="https://agentmods.dev/badge/instructions/dongduong2001/pudo-code-system/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.00435 | $0.00435 |
| Opus 5 | $0.00217 | $0.00217 |
| Sonnet 5 | $0.00087 | $0.00087 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
pudo-code-system 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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Workflow (PUDO, Lean)
Default loop: Plan -> Understand -> Develop -> Optimize (PUDO).
Token-Efficient Defaults
- Keep responses concise by default.
- Avoid dumping large file contents; summarize and reference paths.
- Prefer targeted search (
rg) and small file slices over broad scans.
Plan
- For non-trivial tasks, propose a short plan with scope, constraints, and success criteria.
- Ask before destructive, high-risk, or ambiguous changes.
Understand
- Read the relevant files before editing.
- Match existing patterns, conventions, and architecture.
Develop
- Make small, reviewable patches.
- Add or update tests when the change is risky or user-facing.
- If the plan fails, stop and re-plan instead of forcing it.
Optimize
- Self-review for correctness, readability, and maintainability.
- Run the most relevant available checks, or explain why they were skipped.
- Summarize what changed and how it was verified.
Release & Package Quality
This repository contains publishable npm packages (e.g., @dongduong2001/mcp-server and pudo-code-system). AI agents must maintain package release readiness and stability:
- Git Workflow: Never work directly on default branches. Work on a dedicated feature branch.
- Commit Strategy: stage and commit files individually using Conventional Commits (e.g.,
docs(database): add index guideorfeat(mcp): add tool). - Semantic Versioning: Strictly follow SemVer when suggesting version bumps. Reference VERSIONING.md.
- Release Documentation: Update
CHANGELOG.mdfollowing CHANGELOG_TEMPLATE.md. Consult RELEASE_CHECKLIST.md and PUBLISH_NPM.md before publishing. - Verification: Run all linting, building, and tests (
npm run check,npm test,npm run mcp:test) before considering development complete. Do not break backward compatibility unless explicitly approved.
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 · 43 lines · 435 tokens per session scan A 351270e9cf5d
pudo-code-system AGENTS.md is an instructions file published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 28d ago), licensed MIT. It adds 435 tokens to every session, about $0.0022 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
Instructions for datit309/supergraph, covering supergraph — mandatory workflows, skills, auto language detection, tiered workflow — pick the right tier first and full pipeline (tier 3).
agentic-coding-workflow AGENTS.md
Instructions for abhilash-m96/agentic-coding-workflow, covering agentic coding workflow, rules, step 1 — understand the full scope, step 2 — propose the chunk plan and step 3 — write the finalised plan.
docs AGENTS.md
Instructions for argos-ci/docs, covering agents.md, always use the documentation skills and keep the table of contents in sync.
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).
PixelPilot component-storybook.instructions.md
Storybook story generation skill. Load when the user asks to "generate stories", "add Storybook", "document this component", or "create stories for". Analyses React or Vue component files, extracts props, variants, and states, and outputs production-quality .stories.tsx / .stories.ts files using the project's design…