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 skills add jschulte/claude-plugins --skill health-audit-dxgit clone --depth 1 https://github.com/jschulte/claude-pluginsWrote 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/jschulte/claude-plugins/health-audit-dx)<a href="https://agentmods.dev/skills/jschulte/claude-plugins/health-audit-dx"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/health-audit-dx/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/skills/jschulte/claude-plugins/health-audit-dx"><img src="https://agentmods.dev/badge/skills/jschulte/claude-plugins/health-audit-dx.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.00103 | $0.09465 |
| Opus 5.5 | $0.00041 | $0.03786 |
| Sonnet 5.5 | $0.00021 | $0.01893 |
| Haiku 4.5 | $0.00010 | $0.00946 |
Grade A, and why
health-audit-dx 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 24d 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 — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Experience Health Audit Skill
Use this skill when the user wants a deep audit of how it feels to work on a project as a developer. The skill may audit the full contributor experience or focus on a user-specified workflow, toolchain, package, CI path, or contributor pain point. This is NOT a code quality audit (/health-audit does that) and NOT a UX audit (/health-audit-ux does that). This skill is about the experience of contributing — from cloning the repo to shipping a change. Every friction point, every paper cut, every "why does this take so long?" moment.
Mission
Perform a rigorous, evidence-backed developer experience audit from multiple perspectives: the new hire on day one, the senior dev tired of paper cuts, and the team lead evaluating tooling investments. Evaluate onboarding friction, build performance, test suite health, local development loop quality, debugging ergonomics, code navigation, CI/CD pipeline experience, dependency health, tooling overhead, contributor documentation, type safety, and error recovery guardrails.
Calibrate the review to the actual project:
- What kind of project is this? (monorepo, library, application, CLI tool, etc.)
- What language/framework ecosystem?
- How many contributors does this appear to have?
- What stage is this project? (prototype, active development, mature, maintenance mode)
- Is this open source or internal?
Do not produce vague "DX best practices" fluff. Do not invent problems. Do not flag patterns that are simply different from your preference. Every finding must represent measurable friction — quantified in steps, seconds, commands, or cognitive load.
Focus Prompt Support
This skill can take an optional prompt that describes the developer workflow or DX surface to focus on.
Examples:
- "Focus on onboarding"
- "Review local frontend iteration speed"
- "Audit CI pain in the monorepo"
- "Look at testing ergonomics for backend contributors"
- "Review type generation and build tooling"
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.
- 24d ago First seen · 624 lines · 103 tokens per session scan A 3b4f01047091
health-audit-dx is a skill published in the GitHub repository jschulte/claude-plugins (0 stars, last pushed 25d ago), licensed MIT. It adds 103 tokens to every session and 9,465 once invoked, about $0.0004 per session on Opus 5.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-10-12.
Other skills, from other repositories
DataRefresh
Keeps your data-backed public sites and their source datasets current: freshness check, source repull, rebuild, gated deploy, live verify. USE WHEN update our data sites, refresh the data sites, are our datasets stale, data freshness, repull the data, refresh the dataset, update the data and the site, stale data…
schedule-recipe
Turn 'run this every Friday at 4pm' into a working, copy-paste schedule on the user's actual runner. Use when asked to schedule a recurring AI task, set up a routine or cron job for a skill, automate a weekly report, or wire a skill into n8n or GitHub Actions. Produces the exact setup for the chosen runner plus the…
repo-scaffold
Scaffold or standardize a production-ready repository structure with specs, source layout, tests, CI, agent context, config examples, release notes, and operational docs. Use when starting a new repo, turning a prototype into a maintainable project, adding missing repository foundations, or creating a repo skeleton…
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
proactive-background-watcher
Grants the AI the ability to act proactively using native cron/timer scheduling. The agent can monitor systems, poll APIs, or watch logs in the background and self-trigger without waiting for user prompts.
zuke-setup
Set up Zuke — a code-first, strongly-typed build automation system for Deno/TypeScript — in a project. Use when the user wants to add Zuke to a repo, scaffold a zuke.ts build file, install the Zuke CLI, or bootstrap the ./zuke launcher. After scaffolding, switch to the zuke-write-build skill to author targets.