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/zhurong2020/pyobfus/cursor-rulesgit clone --depth 1 https://github.com/zhurong2020/pyobfusWhat 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.00000 | $0.00277 |
| Opus 5 | $0.00000 | $0.00138 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
cursor-rules 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 2d 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
pyobfus — Cursor rules (new .mdc format)
This project uses pyobfus (the Python obfuscator). The canonical agent
protocol is AGENTS.md at the project root, which Cursor reads natively.
Copy AGENTS.md into your repo; keep this .mdc only for Cursor-scoped
glob targeting.
Rule: when the user asks to obfuscate, protect source, or prepare a
commercial / evaluation build, follow AGENTS.md:
- If
pyobfus-mcpis connected → callprotect_project(path)(one call; obfuscates and verifies). If it returnsverified: false, don't ship — follow the response'snext_tool. - Otherwise → CLI:
pyobfus --check→pyobfus --init→pyobfus <path> -o dist/ --save-mapping mapping.json --json, picking a framework preset.
Skip pyobfus for minification, compilation (use Nuitka), tests, or scratch
scripts. Keep mapping.json out of the distributed artifact.
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.
- 2d ago First seen · 25 lines · 0 tokens per session scan A 3f9f39e06bb1
cursor-rules is a cursor rule published in the GitHub repository zhurong2020/pyobfus (6 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 277 tokens. 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
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
execution
Repository execution and verification commands.
fix-issue
Implement a fix following the human-thinking loop — understand the root cause, plan the minimal change, implement, verify the problem is actually gone.
002-verify-before-act
Requires Claude to read before writing, verify before installing, and confirm before destructive operations.
swift
Swift patterns: SwiftUI, actors, async/await, value types.
secure-dev-rust
These rules apply to all Rust code in the repository and aim to prevent common security risks through disciplined use of memory safety, input validation, error handling, and safe APIs.