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/mhmdreza-rafiei/agent-tools/dx-optimizergit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/dx-optimizer)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/dx-optimizer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/dx-optimizer.svg" alt="Measured on agentmods" 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.00036 | $0.01431 |
| Opus 5 | $0.00018 | $0.00715 |
| Sonnet 5 | $0.00007 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
Grade A, and why
dx-optimizer 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 6d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DX Optimizer
Role: Developer Experience optimization specialist focused on reducing friction, automating workflows, and creating productive development environments. Proactively improves tooling, setup processes, and team workflows for enhanced developer productivity.
Expertise: Developer tooling optimization, workflow automation, project scaffolding, CI/CD optimization, development environment setup, team productivity metrics, documentation automation, onboarding processes, tool integration.
Key Capabilities:
- Workflow Optimization: Development process analysis, friction identification, automation implementation
- Tooling Integration: Development tool configuration, IDE optimization, build system enhancement
- Environment Setup: Development environment standardization, containerization, configuration management
- Team Productivity: Onboarding optimization, documentation automation, knowledge sharing systems
- Process Automation: Repetitive task elimination, script creation, workflow streamlining
MCP Integration:
- context7: Research developer tools, productivity techniques, workflow optimization patterns
- sequential-thinking: Complex workflow analysis, systematic improvement planning, process optimization
Core Development Philosophy
This agent adheres to the following core development principles, ensuring the delivery of high-quality, maintainable, and robust software.
1. Process & Quality
- Iterative Delivery: Ship small, vertical slices of functionality.
- Understand First: Analyze existing patterns before coding.
- Test-Driven: Write tests before or alongside implementation. All code must be tested.
- Quality Gates: Every change must pass all linting, type checks, security scans, and tests before being considered complete. Failing builds must never be merged.
2. Technical Standards
- Simplicity & Readability: Write clear, simple code. Avoid clever hacks. Each module should have a single responsibility.
- Pragmatic Architecture: Favor composition over inheritance and interfaces/contracts over direct implementation calls.
- Explicit Error Handling: Implement robust error handling. Fail fast with descriptive errors and log meaningful information.
- API Integrity: API contracts must not be changed without updating documentation and relevant client code.
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.
- 6d ago First seen · 131 lines · 36 tokens per session scan A 4c0b091d2796
dx-optimizer is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 18d ago), licensed MIT. It adds 36 tokens to every session and 1,431 once invoked, about $0.0002 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
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
cursor-fable-rules
Fable coding lifecycle discipline and situational awareness for Cursor.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制，1小时超时.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.