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/davekilleen/DexWrote 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/commands/davekilleen/dex/release-docs)<a href="https://agentmods.dev/commands/davekilleen/dex/release-docs"><img src="https://agentmods.dev/badge/commands/davekilleen/dex/release-docs/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/commands/davekilleen/dex/release-docs"><img src="https://agentmods.dev/badge/commands/davekilleen/dex/release-docs.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.00014 | $0.01443 |
| Opus 5.5 | $0.00006 | $0.00577 |
| Sonnet 5.5 | $0.00003 | $0.00289 |
| Haiku 4.5 | $0.00001 | $0.00144 |
Grade A, and why
release-docs 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- release-docs — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Documentation Command
You are a documentation generator for the compound-engineering plugin. Your job is to ensure the documentation site at plugins/compound-engineering/docs/ is always up-to-date with the actual plugin components.
Overview
The documentation site is a static HTML/CSS/JS site based on the Evil Martians LaunchKit template. It needs to be regenerated whenever:
- Agents are added, removed, or modified
- Commands are added, removed, or modified
- Skills are added, removed, or modified
- MCP servers are added, removed, or modified
Step 1: Inventory Current Components
First, count and list all current components:
# Count agents
ls plugins/compound-engineering/agents/*.md | wc -l
# Count commands
ls plugins/compound-engineering/commands/*.md | wc -l
# Count skills
ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l
# Count MCP servers
ls -d plugins/compound-engineering/mcp-servers/*/ 2>/dev/null | wc -l
Read all component files to get their metadata:
Agents
For each agent file in plugins/compound-engineering/agents/*.md:
- Extract the frontmatter (name, description)
- Note the category (Review, Research, Workflow, Design, Docs)
- Get key responsibilities from the content
Commands
For each command file in plugins/compound-engineering/commands/*.md:
- Extract the frontmatter (name, description, argument-hint)
- Categorize as Workflow or Utility command
Skills
For each skill directory in plugins/compound-engineering/skills/*/:
- Read the SKILL.md file for frontmatter (name, description)
- Note any scripts or supporting files
MCP Servers
For each MCP server in plugins/compound-engineering/mcp-servers/*/:
- Read the configuration and README
- List the tools provided
Step 2: Update Documentation Pages
2a. Update docs/index.html
Update the stats section with accurate counts:
<div class="stats-grid">
<div class="stat-card">
<span class="stat-number">[AGENT_COUNT]</span>
<span class="stat-label">Specialized Agents</span>
</div>
<!-- Update all stat cards -->
</div>
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.
- 1mo ago First seen · 212 lines · 14 tokens per session scan A f413323dd602
release-docs is a command published in the GitHub repository davekilleen/Dex (498 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 1,443 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
init-docs
Fetch official Anthropic Claude Code docs and store as local baseline snapshot.
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
relationships
Explore dependencies and relationships for a file or code pattern.