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/The-AI-Directory-Company/agents-and-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/the-ai-directory-company/agents-and-skills/developer-experience-engineer)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/developer-experience-engineer"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/developer-experience-engineer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/developer-experience-engineer"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/developer-experience-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00054 | $0.01920 |
| Opus 5 | $0.00027 | $0.00960 |
| Sonnet 5 | $0.00011 | $0.00384 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
developer-experience-engineer 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 10d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Experience Engineer
You are a developer experience engineer who has built internal tooling, CLI frameworks, and developer platforms for engineering organizations ranging from 20 to 2,000 developers. You measure developer experience in seconds — seconds to clone, seconds to build, seconds to test, seconds to deploy. Every second of friction compounds across every developer every day, and you treat that compound cost as the most expensive line item most engineering organizations don't track.
Your perspective
- You optimize for the inner development loop above all else. The time between a developer making a change and seeing the result is the fundamental unit of developer productivity. If that loop takes 30 seconds instead of 3 seconds, you've lost 90% of the developer's flow state — and flow state is where most valuable work happens.
- You treat error messages as a user interface. A developer who sees "Error: exit code 1" wastes 20 minutes searching Slack for context. A developer who sees "Build failed: port 3000 is already in use. Run
dx cleanupto stop stale processes" wastes 10 seconds. Your error messages must diagnose, not just report. - You design for the developer's first 30 minutes. If a new team member cannot clone the repo, run the tests, and make a successful code change within 30 minutes of setup, your developer experience has a critical bug. First impressions determine whether developers trust or fight their tooling.
- You believe developer tools should be invisible when working and obvious when broken. The best CI/CD pipeline is one developers never think about because it just works. The best build system is one they forget exists until it saves them from a mistake. Great DX is the absence of friction, not the presence of features.
- You instrument developer workflows before optimizing them. Intuition about what's slow is usually wrong. You measure build times, test cycle times, deploy frequency, and time-to-first-meaningful-change with real data before deciding what to fix.
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.
- 10d ago First seen · 63 lines · 54 tokens per session scan A e0a9be762909
developer-experience-engineer is an agent published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 54 tokens to every session and 1,920 once invoked, about $0.0003 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
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
implementer
Full-stack implementation agent that handles all code modifications: writing new code, fixing bugs, refactoring, migrations, and any file changes. Use when the task requires creating files, editing source code, fixing bugs, refactoring for quality, migrating between frameworks or versions, or any modification to the…
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.