dx-audit

dx-audit is a skill for Claude Code, Codex from OutlineDriven/odin-claude-plugin. It costs 56 tokens per session (1,656 once invoked), scanned A, a copy of dx-audit, Apache-2.0.

A read-only review of the parts of a CLI, software development kit, library, or package that developers use directly.

In plain words
What is it for?
It helps produce severity-ranked findings and suggested fixes for developer-facing behavior and documentation.
Why use it?
It finds confusing commands, errors, public interfaces, configuration, or onboarding problems without changing the project.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the odin-code plugin — 60 skills shipped together

Good fit It helps produce severity-ranked findings and suggested fixes for developer-facing behavior and documentation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/outlinedriven/odin-claude-plugin/dx-audit
Install

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.

Any agent
npx skills add OutlineDriven/odin-claude-plugin --skill dx-audit
Clone the repo
git clone --depth 1 https://github.com/OutlineDriven/odin-claude-plugin

Made for: Claude Code, Codex.

Or install odin-code, the plugin that ships this one along with the rest of its 60 skills.

Wrote 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.

agentmods badge for dx-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/dx-audit/github.svg)](https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/dx-audit)
Your own site
<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/dx-audit"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/dx-audit/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.

agentmods 80×15 button for dx-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/dx-audit"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/dx-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,656 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00056 $0.01656
Opus 5 $0.00028 $0.00828
Sonnet 5 $0.00011 $0.00331
Haiku 4.5 $0.00006 $0.00166

Measured 6d ago against content hash cc7b3c48769d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

dx-audit 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 6d 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.

Origin

This is a copy

100% identical to dx-audit — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

plugins/odin-code/skills/dx-audit/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

DX audit

Contract

Field Bound contract
Trigger Audit my CLI, make this CLI agent-friendly, is this API ergonomic, SDK review, library DX, developer onboarding
Authority Read-only. No file, VCS, credential, paid, published, deployed, or remote mutation. Produces recommended fixes as chat output; never applies them.
Side effect Chat output only: severity-tiered findings with root-cause analysis and committable fix recommendations. No repository mutation.
Done Returns bounded, root-caused DX findings for the smallest relevant public surface.

Inputs

Required: the developer-facing surface to audit, a named CLI command, exported API, package, error path, config loader, or the changed public surface from a diff.

Optional: a comparison baseline or prior release contract when the diff changes a public export, signature, or return shape.

Procedure

  1. Lock scope. Choose the narrowest mode: targeted (the default; inspect and report on the named or changed public surface) or exhaustive (only when the user explicitly asks for the whole package or every public surface). Write a one-line scope receipt that names the mode, surfaces, selected audit categories, and exclusions (end-user UI, docs prose, repo architecture, private internals). Done when: a one-line scope receipt names the mode, surfaces, categories, and exclusions.
  2. Identify the public surface. Default to git diff against the repository's normal base, keeping only changed files reachable through a public entry point. With no useful diff, use the command, export, package, error, or config named by the user. Public reachability comes from package.json exports/bin, a command registry, an exported type, a documented config loader, or an observed error path. Do not audit a private helper unless a public caller exposes its behavior. Done when: the public surface is identified from the diff or user-named entry point.
  3. Follow the evidence ladder, then stop. (a) Read local instructions, the relevant manifest, and the diff or named entry point. (b) Trace only direct public dependencies and the nearest tests that establish behavior. (c) For a CLI, use a small safe probe set when useful: --help, --version, one success path, and one invalid-input path. Do not trigger a real mutation merely to test DX. (d) Check a prior release contract only when the diff changes a public export, signature, or return shape. Stop when the behavior is proven, disproven, private, or outside scope. Do not browse general best-practice articles, inventory unrelated apps, or build static repo maps. Done when: behavior is proven, disproven, private, or outside scope with no unnecessary browsing.
  4. Select audit categories candidate-first. Map locked surfaces to these categories; applicability outranks global priority:

Read the full file on GitHub · 54 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 6d ago First seen · 54 lines · 56 tokens per session scan A cc7b3c48769d

Subscribe to this mod's changes

dx-audit is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed yesterday), licensed Apache-2.0. It adds 56 tokens to every session and 1,656 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to dx-audit, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens