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/nphausg/ai-agent-skills/general_clean_code_principlesgit clone --depth 1 https://github.com/nphausg/ai-agent-skillsWhat 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.00006 | $0.00087 |
| Opus 5 | $0.00003 | $0.00044 |
| Sonnet 5 | $0.00001 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
general_clean_code_principles 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
- Keep functions small and focused
- One class per file
- Limit function size to 20 lines if possible
- Avoid long parameter lists (max 3–4 parameters)
- Minimize nested control structures
- Remove commented-out code before committing
- Prefer meaningful names over comments
- DRY (Don’t Repeat Yourself): extract duplication
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 · 13 lines · 6 tokens per session scan A e4a10d115a2e
general_clean_code_principles is a cursor rule published in the GitHub repository nphausg/ai-agent-skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 6 tokens to every session and 87 once invoked, about $0.0000 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
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
hono-gateway
Hono gateway Worker rules - middleware order, observability, zValidator, thin handlers, service bindings.
workers-config
Wrangler config rules - secrets vs vars, generated types, RPC typing, fail-closed expectations.
type-inference
Derive TypeScript types from Zod schemas - no hand-written interfaces for wire shapes.
general
You are running in Cursor IDE. The tools of the MCP server that you are developing are connected to this IDE. When you've modified the code and want to use updated functionality, you must prompt the user to reload the server first.
paperfit
PaperFit project rule for LaTeX visual typesetting optimization.