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 skills/mickeyyaya/refactoring-skills/developer-experience-patternsnpx skills add mickeyyaya/refactoring-skills --skill developer-experience-patternsgit clone --depth 1 https://github.com/mickeyyaya/refactoring-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/skills/mickeyyaya/refactoring-skills/developer-experience-patterns)<a href="https://agentmods.dev/skills/mickeyyaya/refactoring-skills/developer-experience-patterns"><img src="https://agentmods.dev/badge/skills/mickeyyaya/refactoring-skills/developer-experience-patterns.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 | $0.00081 | $0.05278 |
| Opus 5 | $0.00041 | $0.02639 |
| Sonnet 5 | $0.00016 | $0.01056 |
| Haiku 4.5 | $0.00008 | $0.00528 |
Grade A, and why
developer-experience-patterns scanned grade A 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 5d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
import { execSync } from 'child_process'; How it starts
The opening of the file, as written. The whole thing — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Experience Patterns
Overview
Poor developer experience compounds over time: slow builds frustrate contributors, undocumented environments block onboarding, and inconsistent tooling creates invisible silos. Use this guide when designing internal platforms, reviewing build configurations, auditing onboarding docs, or evaluating the ergonomics of a developer-facing API.
When to use: Setting up a new monorepo, auditing CI pipeline speed, designing an internal developer platform (IDP), evaluating a new service template, reviewing a contributing guide, or assessing why engineers avoid a particular tool.
Quick Reference
| Pattern | Core Idea | Primary Red Flag |
|---|---|---|
| Monorepo Tooling | Nx / Turborepo compute affected builds from dependency graph | Rebuilding all packages on every commit |
| Dev Containers | Reproducible environment declared as code via .devcontainer |
"Works on my machine" — setup differs per laptop |
| Golden Path | Opinionated service templates and internal platform reduce decision fatigue | Every team reinvents CI config from scratch |
| Local-Prod Parity | Seed scripts, test-data factories, and env management mirror production data shapes | Tests pass locally, fail in CI due to missing seed data |
| Fast Feedback Loops | Hot reload, incremental builds, test watch mode surface errors in seconds | 30-minute build for a one-line change |
| DX-First API Design | Ergonomic SDKs, descriptive errors, auto-generated docs make APIs self-explaining | Callers must read the source to understand error shapes |
| Developer Onboarding | Setup scripts, contributing guides, and ADRs reduce time-to-first-PR | New hire takes two weeks to run the app locally |
| DX Anti-Patterns | Tribal knowledge, manual setup steps, flaky environments erode confidence | Undocumented environment variables required at runtime |
Patterns in Detail
1. Monorepo Tooling (Nx, Turborepo, Affected Builds)
A monorepo collocates multiple packages or services in one repository. The key win is affected builds: only rebuild and retest the packages that changed, computed from the dependency graph.
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.
- 5d ago First seen · 571 lines · 81 tokens per session scan A e7fd1e66ded7
developer-experience-patterns is a skill published in the GitHub repository mickeyyaya/refactoring-skills (6 stars, last pushed 5mo ago), licensed MIT. It adds 81 tokens to every session and 5,278 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
whendone-plus
Automatically notify the user when long-running terminal commands finish (npm test, docker build, git push, etc.). The agent monitors command execution and sends a desktop notification on completion if the command ran longer than threshold (default 10s). Use when user asks to "notify me when done", "desktop…
gobbler-setup
Installs, configures, and troubleshoots Gobbler. Triggers on install gobbler, setup, not working, connection refused, Docker/service failures, ffmpeg problems, browser relay failures, or diagnostic requests.
system-environment-setup
Build reproducible developer environments for real projects: local toolchains, runtime versions, Docker Compose or dev containers, onboarding flows, local service parity, bootstrap scripts, and environment troubleshooting. Use when the user needs a repo to run consistently across machines, containers, or staged…
vscode-workspace-setup
Configures VS Code workspaces with optimal settings, extensions, tasks, and debugging for team consistency. Use when users request "VS Code setup", "workspace settings", "team VS Code config", "editor configuration", or "devcontainer setup".
makefile
Create a Makefile with central commands for a project — build, test, lint, deploy, docker, and dev workflow commands. Use when asked to add a Makefile, standardize project commands, or create dev tooling.
terminal-execution
Guide for using the execute tool to run shell commands in workspace. Use when agent needs to: build/test code, run scripts, check system status, install dependencies, or execute deployment commands.