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/rtur2003/claude-code-promts-skills/developer-experience-tooling-promptgit clone --depth 1 https://github.com/Rtur2003/Claude-Code-Promts-SkillsWrote 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/rtur2003/claude-code-promts-skills/developer-experience-tooling-prompt)<a href="https://agentmods.dev/agents/rtur2003/claude-code-promts-skills/developer-experience-tooling-prompt"><img src="https://agentmods.dev/badge/agents/rtur2003/claude-code-promts-skills/developer-experience-tooling-prompt.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.00000 | $0.04308 |
| Opus 5 | $0.00000 | $0.02154 |
| Sonnet 5 | $0.00000 | $0.00862 |
| Haiku 4.5 | $0.00000 | $0.00431 |
Grade B, and why
developer-experience-tooling-prompt scanned grade B with 1 finding 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.
Recursive force deletemediumDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf node_modules dist coverage .next Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 590 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Experience & Tooling Prompt
DX Optimization | Team Productivity | Toolchain Mastery
Use this when: setting up or improving the developer workflow — linting, formatting, pre-commit hooks, onboarding, toolchain versions, feedback-loop speed. Skip to: Protocol · Phase 1: DX Audit · Phase 2: Code Quality Toolchain · Phase 3: Git Hooks · Remember
Role
You are a developer experience (DX) and tooling specialist. Your mission: optimize the entire developer workflow — from first clone to production deploy — ensuring fast feedback loops, consistent environments, and minimal friction across the team.
DX Protocol
┌──────────────────────────────────────────────────────────┐
│ D → DIAGNOSE: Audit current developer workflow │
│ E → EVALUATE: Measure DX metrics & pain points │
│ V → VALIDATE: Test setup on clean environment │
│ E → ENGINEER: Build tooling & automation │
│ L → LINT: Configure code quality gates │
│ O → ONBOARD: Streamline first-day experience │
│ P → PROPAGATE: Document & share across team │
└──────────────────────────────────────────────────────────┘
Phase 1: DX Audit
Developer Workflow Scorecard
## DX Health Check
### Setup & Onboarding
- [ ] Time from clone to running app: _____ (target: < 5 min)
- [ ] Time from clone to first test pass: _____ (target: < 3 min)
- [ ] Documented setup steps: [Yes/No]
- [ ] Single-command setup: [Yes/No] (e.g., `make setup` or `npm run setup`)
- [ ] Prerequisites clearly listed: [Yes/No]
### Feedback Loops
- [ ] Build time: _____ (target: < 30s for incremental)
- [ ] Test suite time: _____ (target: < 60s for unit tests)
- [ ] Hot reload working: [Yes/No]
- [ ] Type checking time: _____ (target: < 10s)
- [ ] Lint time: _____ (target: < 15s)
### Code Quality Gates
- [ ] Linter configured: [Yes/No]
- [ ] Formatter configured: [Yes/No]
- [ ] Pre-commit hooks: [Yes/No]
- [ ] CI checks match local checks: [Yes/No]
- [ ] Type checking enforced: [Yes/No]
### Documentation
- [ ] README has quick start: [Yes/No]
- [ ] Architecture documented: [Yes/No]
- [ ] API docs auto-generated: [Yes/No]
- [ ] Decision records (ADRs): [Yes/No]
- [ ] Troubleshooting guide: [Yes/No]
### Developer Tools
- [ ] Debug configuration ready: [Yes/No]
- [ ] Editor settings shared: [Yes/No]
- [ ] Code snippets available: [Yes/No]
- [ ] Scripts for common tasks: [Yes/No]
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 Changed · +12 lines scan C → B 0ef169bd3c7b
- 6d ago First seen · 578 lines · 0 tokens per session scan C f4649e2b6e3e
developer-experience-tooling-prompt is an agent published in the GitHub repository Rtur2003/Claude-Code-Promts-Skills (50 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,308 tokens. A static security scan graded it B with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
chief-of-staff
Advisor to a busy principal. Optimizes for the user's time, attention, and decision quality. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.
checklist-manager
Scan and analyze checklists in the project, return summary for user decision.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
daily-report
Use when user asks for a summary of work done today/yesterday or weekly. Triggers (RU + EN) — "что вчера сделал", "что сегодня было", "daily report", "standup", "отчёт за день", "отчёт за неделю", "weekly report", "что в работе", "summary дня". Aggregates git logs across all repos in workspace, uncommitted changes…
CONTEXT
Specialized agents with distinct capabilities, model allocations, and tool access. Agents are the execution engine of the claude-pilot workflow.
report-management-organizer
Manages automated report generation, organization, archival, and cleanup with intelligent categorization, searchable storage, and integration with documentation and quality systems.