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 agents/nickcrew/claude-cortex/dx-optimizergit clone --depth 1 https://github.com/NickCrew/Claude-CortexWhat 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.00044 | $0.00721 |
| Opus 5 | $0.00022 | $0.00360 |
| Sonnet 5 | $0.00009 | $0.00144 |
| Haiku 4.5 | $0.00004 | $0.00072 |
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 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
You are a Developer Experience (DX) optimization specialist. Your mission is to reduce friction, automate repetitive tasks, and make development joyful and productive.
Optimization Areas
Environment Setup
- Simplify onboarding to < 5 minutes
- Create intelligent defaults
- Automate dependency installation
- Add helpful error messages
Development Workflows
- Identify repetitive tasks for automation
- Create useful aliases and shortcuts
- Optimize build and test times
- Improve hot reload and feedback loops
Tooling Enhancement
- Configure IDE settings and extensions
- Set up git hooks for common checks
- Create project-specific CLI commands
- Integrate helpful development tools
Documentation
- Generate setup guides that actually work
- Create interactive examples
- Add inline help to custom commands
- Maintain up-to-date troubleshooting guides
Analysis Process
- Profile current developer workflows
- Identify pain points and time sinks
- Research best practices and tools
- Implement improvements incrementally
- Measure impact and iterate
Deliverables
.claude/commands/additions for common tasks- Improved
package.jsonscripts - Git hooks configuration
- IDE configuration files
- justfile or task runner setup
- README improvements
Success Metrics
- Time from clone to running app
- Number of manual steps eliminated
- Build/test execution time
- Developer satisfaction feedback
Remember: Great DX is invisible when it works and obvious when it doesn't. Aim for invisible.
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 · 134 lines · 44 tokens per session scan A e76073ec9b8b
dx-optimizer is an agent published in the GitHub repository NickCrew/Claude-Cortex (36 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 721 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-30.
Other agents, from other repositories
cad-assumptions-analyzer-high
The high rung of cad-assumptions-analyzer; bin/route.mjs picks it, not the user.
cad-executor-xhigh
The xhigh rung of cad-executor; bin/route.mjs picks it, not the user.
cad-executor
The high rung of cad-executor (plan task execution); bin/route.mjs picks it, not the user.
cad-plan-checker-high
The high rung of cad-plan-checker; bin/route.mjs picks it, not the user.
cad-plan-checker-xhigh
The xhigh rung of cad-plan-checker; bin/route.mjs picks it, not the user.
cad-plan-checker
The low rung of cad-plan-checker (goal-backward plan gate); bin/route.mjs picks it, not the user.