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.
git 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/cursorrules)<a href="https://agentmods.dev/rules/dongduong2001/pudo-code-system/cursorrules"><img src="https://agentmods.dev/badge/rules/dongduong2001/pudo-code-system/cursorrules/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/dongduong2001/pudo-code-system/cursorrules"><img src="https://agentmods.dev/badge/rules/dongduong2001/pudo-code-system/cursorrules.svg" alt="Reviewed on agentmods" width="80" 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.00208 | $0.00208 |
| Opus 5.5 | $0.00083 | $0.00083 |
| Sonnet 5.5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
cursorrules 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 1mo 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 Methodology Rules
Legacy Cursor rule file. Prefer the Project Rules templates in cursor/.cursor/rules/*.mdc for current Cursor versions. Keep this file for older Cursor workspaces that still read .cursorrules.
Always follow the PUDO (Plan -> Understand -> Develop -> Optimize) framework.
1. Plan
- Do not generate implementation code right away.
- Propose an implementation plan first.
- Explicitly outline scope, constraints, and success criteria.
2. Understand
- Read related files and context before writing code.
- Match existing code patterns, naming conventions, and architecture.
3. Develop
- Work step-by-step.
- Write tests alongside feature code.
- Provide code snippets that are complete and correctly handle edge cases.
4. Optimize
- Self-review your code before finishing.
- Check for performance bottlenecks, dead code, and missing documentation.
Embrace iterative loops: if an approach fails during Develop, pause and re-Plan.
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.
- 1mo ago First seen · 26 lines · 208 tokens per session scan A e1c17bd5d043
cursorrules is a cursor rule published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 9d ago), licensed MIT. It adds 208 tokens to every session, about $0.0008 per session on Opus 5.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
data-science
Rules for data science, ML, and Jupyter notebook work.
java-kotlin
Rules applied when working in Java or Kotlin files (incl. Android).
nextjs
Rules for Next.js projects (App Router and Pages Router).
html-css
Rules for HTML, CSS, and styling files.
php
Rules applied when working in PHP files (incl. Laravel, Symfony, WordPress).
shell
Rules for shell scripts (bash, zsh, sh, PowerShell).