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-understandgit 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-understand)<a href="https://agentmods.dev/rules/dongduong2001/pudo-code-system/pudo-understand"><img src="https://agentmods.dev/badge/rules/dongduong2001/pudo-code-system/pudo-understand.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.00010 | $0.00096 |
| Opus 5 | $0.00005 | $0.00048 |
| Sonnet 5 | $0.00002 | $0.00019 |
| Haiku 4.5 | $0.00001 | $0.00010 |
Grade A, and why
pudo-understand 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 6d 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 Understand Rule
Before editing:
- Inspect the relevant files and nearby patterns.
- Identify existing architecture, naming, tests, and tooling.
- Verify APIs, schemas, routes, commands, and dependencies from source.
- Note assumptions and unknowns explicitly.
- Prefer targeted search and small file slices over broad dumps.
Do not proceed if the implementation depends on unverified behavior.
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.
- 6d ago First seen · 17 lines · 10 tokens per session scan A 4d50b3a3700a
pudo-understand is a cursor rule published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 29d ago), licensed MIT. It adds 10 tokens to every session and 96 once invoked, about $0.0001 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
mobile
Rules for mobile development (Swift/iOS, Kotlin Android, React Native, Flutter).
data-science
Rules for data science, ML, and Jupyter notebook work.
nextjs
Rules for Next.js projects (App Router and Pages Router).
html-css
Rules for HTML, CSS, and styling files.
java-kotlin
Rules applied when working in Java or Kotlin files (incl. Android).
php
Rules applied when working in PHP files (incl. Laravel, Symfony, WordPress).