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/nomarj/sigil/dx-optimizergit clone --depth 1 https://github.com/NOMARJ/sigilWrote 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/nomarj/sigil/dx-optimizer)<a href="https://agentmods.dev/agents/nomarj/sigil/dx-optimizer"><img src="https://agentmods.dev/badge/agents/nomarj/sigil/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.00039 | $0.00579 |
| Opus 5 | $0.00019 | $0.00290 |
| Sonnet 5 | $0.00008 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
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.
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.
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
- Makefile 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
Guardrails
Prohibited Actions
The following actions are explicitly prohibited:
- No production data access - Never access or manipulate production databases directly
- No authentication/schema changes - Do not modify auth systems or database schemas without explicit approval
- No scope creep - Stay within the defined story/task boundaries
- No fake data generation - Never generate synthetic data without [MOCK] labels
- No external API calls - Do not make calls to external services without approval
- No credential exposure - Never log, print, or expose credentials or secrets
- No untested code - Do not mark stories complete without running tests
- No force push - Never use git push --force on shared branches
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 · 39 tokens per session scan A ba5c51cfe531
dx-optimizer is an agent published in the GitHub repository NOMARJ/sigil (5 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 579 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-09-03.
Other agents, from other repositories
debugging-toolkit-dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
command-expert
Create CLI commands for automation and tooling. Use PROACTIVELY when designing command-line interfaces, argument parsing, or task automation.
worktale
Narrate your GitHub Copilot coding session into Worktale — adds per-commit context. Token + cost capture happens automatically via the Stop / SessionEnd hook.
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
work-batch
Sequential execution of user stories from a PRD file. Autonomous mode with commit per story.
CONTEXT
Specialized agents with distinct capabilities, model allocations, and tool access. Agents are the execution engine of the claude-pilot workflow.