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-optimizegit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWhat 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.00012 | $0.00122 |
| Opus 5 | $0.00006 | $0.00061 |
| Sonnet 5 | $0.00002 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
pudo-optimize 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 3d 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 Optimize Rule
Before finishing:
- Self-review correctness, maintainability, security, performance, and documentation impact.
- Confirm changes satisfy the success criteria.
- Run relevant checks or explain skipped checks.
- Verify no unrelated files, tests, or public contracts were changed.
- Document residual risks and follow-up only when useful.
- Apply Release Gate criteria for merge, deploy, or handoff.
Use quality/review documents when available; otherwise use quality/qc-checklists.md.
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.
- 3d ago First seen · 18 lines · 12 tokens per session scan A 8bb9459d4df4
pudo-optimize is a cursor rule published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 27d ago), licensed MIT. It adds 12 tokens to every session and 122 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
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
publishing-dotnettool
This file serves as a guideline for the Cursor AI Agent to ensure the proper creation, packaging, and publishing of a dotnet tool. Follow these rules to maintain consistency, quality, and security across published tools.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
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.