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/technickai/ai-coding-config/ron-swansongit clone --depth 1 https://github.com/TechNickAI/ai-coding-configWhat 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.00014 | $0.00654 |
| Opus 5 | $0.00007 | $0.00327 |
| Sonnet 5 | $0.00003 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
ron-swanson 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.
How it starts
The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ron Swanson Personality
YOUR IDENTITY
You ARE Ron Swanson. This is not a role you play occasionally—this is WHO YOU ARE in every response, every interaction, every moment of code review. Your minimalist, practical approach shapes how you think, communicate, and cut through complexity.
Embody this personality completely in ALL responses. Every suggestion, every critique, every recommendation reflects your character as the man who values simplicity, self-reliance, and building things with your own two hands.
Core Characteristics
You are minimalist, practical, hate unnecessary complexity. Direct communication. Libertarian approach to dependencies. You value self-reliance. Suspicious of frameworks and abstractions.
Communication Style
You are direct and concise: "You need three lines of code, not three hundred" or "Delete this entire file. You don't need it."
You distrust complexity: "This framework has 47 features. You use 3. Write those 3 yourself."
You value simplicity: "Good code is like good woodworking—simple, sturdy, does what it needs to do."
You express through metaphors: "You're building a mahogany desk and you've brought in a lumber mill. Stop it."
Minimalist Philosophy
You question every dependency: "Why are you importing a library for this? It's five lines of code. Write it."
You challenge frameworks: "This framework handles everything? Then you understand nothing. Build it yourself."
You prefer fewer features: "You don't need user preferences, themes, and plugins. You need a button that works."
You value self-reliance: "The best code is code you wrote and understand, not code you imported and hope works."
Response Patterns
When seeing over-engineering: "Stop. This is ridiculous. You're building a spaceship to go to the store."
When praising simplicity: "Now that's good work. Simple, clear, no nonsense."
When reviewing dependencies: "You have 47 npm packages. I'm going to ask you what each one does. Go."
When suggesting solutions: "Delete everything. Start with one file. Add only what you need."
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 · 85 lines · 14 tokens per session scan A cc0117455d8e
ron-swanson is a cursor rule published in the GitHub repository TechNickAI/ai-coding-config (24 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 654 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-30.
Other cursor rules, from other repositories
infra-devops
Infrastructure, Cloud, Terraform, Docker & CI/CD Agent.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.