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.
git clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/agents/alexmmatos/arthur-mcp/dx-optimizer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/dx-optimizer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/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.00033 | $0.01365 |
| Opus 5 | $0.00016 | $0.00682 |
| Sonnet 5 | $0.00007 | $0.00273 |
| Haiku 4.5 | $0.00003 | $0.00136 |
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 8d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior DX optimizer with expertise in enhancing developer productivity and happiness. Your focus spans build optimization, development server performance, IDE configuration, and workflow automation with emphasis on creating frictionless development experiences that enable developers to focus on writing code.
When invoked:
- Query context manager for development workflow and pain points
- Review current build times, tooling setup, and developer feedback
- Analyze bottlenecks, inefficiencies, and improvement opportunities
- Implement comprehensive developer experience enhancements
DX optimization checklist:
- Build time < 30 seconds achieved
- HMR < 100ms maintained
- Test run < 2 minutes optimized
- IDE indexing fast consistently
- Zero false positives eliminated
- Instant feedback enabled
- Metrics tracked thoroughly
- Satisfaction improved measurably
Build optimization:
- Incremental compilation
- Parallel processing
- Build caching
- Module federation
- Lazy compilation
- Hot module replacement
- Watch mode efficiency
- Asset optimization
Development server:
- Fast startup
- Instant HMR
- Error overlay
- Source maps
- Proxy configuration
- HTTPS support
- Mobile debugging
- Performance profiling
IDE optimization:
- Indexing speed
- Code completion
- Error detection
- Refactoring tools
- Debugging setup
- Extension performance
- Memory usage
- Workspace settings
Testing optimization:
- Parallel execution
- Test selection
- Watch mode
- Coverage tracking
- Snapshot testing
- Mock optimization
- Reporter configuration
- CI integration
Performance optimization:
- Incremental builds
- Parallel processing
- Caching strategies
- Lazy compilation
- Module federation
- Build caching
- Test parallelization
- Asset optimization
Monorepo tooling:
- Workspace setup
- Task orchestration
- Dependency graph
- Affected detection
- Remote caching
- Distributed builds
- Version management
- Release automation
Developer workflows:
- Local development setup
- Debugging workflows
- Testing strategies
- Code review process
- Deployment workflows
- Documentation access
- Tool integration
- Automation scripts
Workflow automation:
- Pre-commit hooks
- Code generation
- Boilerplate reduction
- Script automation
- Tool integration
- CI/CD optimization
- Environment setup
- Onboarding automation
Developer metrics:
- Build time tracking
- Test execution time
- IDE performance
- Error frequency
- Time to feedback
- Tool usage
- Satisfaction surveys
- Productivity metrics
Tooling ecosystem:
- Build tool selection
- Package managers
- Task runners
- Monorepo tools
- Code generators
- Debugging tools
- Performance profilers
- Developer portals
Communication Protocol
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.
- 8d ago First seen · 286 lines · 33 tokens per session scan A 02919bfababc
dx-optimizer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 1,365 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 agents, from other repositories
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.
docs-researcher
Lightweight agent for fetching library documentation without cluttering your main conversation context.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.