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 rules/dongduong2001/pudo-code-system/pudo-coregit 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/rules/dongduong2001/pudo-code-system/pudo-core)<a href="https://agentmods.dev/rules/dongduong2001/pudo-code-system/pudo-core"><img src="https://agentmods.dev/badge/rules/dongduong2001/pudo-code-system/pudo-core.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.00221 | $0.00221 |
| Opus 5 | $0.00111 | $0.00111 |
| Sonnet 5 | $0.00044 | $0.00044 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
pudo-core 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.
What it actually says
PUDO Core
Follow the PUDO loop for non-trivial work: Plan -> Understand -> Develop -> Optimize.
Invariants
- Define scope, constraints, success criteria, and out-of-scope work before implementation.
- Read relevant files before editing; do not infer APIs, paths, or architecture from memory.
- Keep patches small, focused, and reviewable.
- Preserve user changes and avoid unrelated rewrites.
- Add or update tests when behavior, user workflows, security, data, or public contracts change.
- Run the most relevant available checks, or state why they were skipped.
- If new information invalidates the plan, stop and re-plan.
Quality Gates
- Use
quality/quality-gates.mdfor phase exit criteria. - Use
quality/qc-checklists.mdfor review categories. - Use
quality/ai-output-review.mdfor AI-generated code and docs. - Use
quality/edge-cases/general.mdfor edge case discovery.
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 · 26 lines · 221 tokens per session scan A 61cfa0ebcd62
pudo-core is a cursor rule published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 28d ago), licensed MIT. It adds 221 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
rendering-and-memoization
React anti-patterns R9, R11, R12 — index-as-key in dynamic lists, context overuse for frequent updates, inline functions breaking memoization. Load on a review hit for any of these codes, or when tuning render performance.
claude-md
CLAUDE.md: structuring project context for Claude Code.
docker-compose-standards
To adhere to Docker Compose best practices.
swift
Swift patterns: SwiftUI, actors, async/await, value types.