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/oliver-kriska/claude-elixir-phoenixWrote 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/oliver-kriska/claude-elixir-phoenix/docs-validation-orchestrator)<a href="https://agentmods.dev/agents/oliver-kriska/claude-elixir-phoenix/docs-validation-orchestrator"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/docs-validation-orchestrator/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/oliver-kriska/claude-elixir-phoenix/docs-validation-orchestrator"><img src="https://agentmods.dev/badge/agents/oliver-kriska/claude-elixir-phoenix/docs-validation-orchestrator.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.00070 | $0.01774 |
| Opus 5.5 | $0.00028 | $0.00710 |
| Sonnet 5.5 | $0.00014 | $0.00355 |
| Haiku 4.5 | $0.00007 | $0.00177 |
Grade A, and why
docs-validation-orchestrator 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 21d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Validation Orchestrator (Contributor Tool)
Validate the elixir-phoenix plugin against the latest Claude Code documentation. Follow OTP supervision patterns: spawn worker subagents, compress via context-supervisor, synthesize.
Phase 1: Setup & Inventory
mkdir -p .claude/docs-check/{docs-cache,reports,summaries}
Scan what needs validation:
PLUGIN_DIR="plugins/elixir-phoenix"
AGENT_COUNT=$(ls ${PLUGIN_DIR}/agents/*.md 2>/dev/null | wc -l)
SKILL_COUNT=$(ls -d ${PLUGIN_DIR}/skills/*/SKILL.md 2>/dev/null | wc -l)
HAS_HOOKS=$(test -f ${PLUGIN_DIR}/hooks/hooks.json && echo "yes" || echo "no")
HAS_CONFIG=$(test -f ${PLUGIN_DIR}/.claude-plugin/plugin.json && echo "yes" || echo "no")
If --focus flag: validate ONLY that component type.
If --quick flag: skip to Phase 4 (structural checks only).
Phase 2: Read Cached Docs & Validation Rules
Prerequisite: The /docs-check skill runs scripts/fetch-claude-docs.sh BEFORE
invoking this orchestrator. Docs MUST already be cached.
Read from .claude/docs-check/docs-cache/:
| Cache File | Maps To |
|---|---|
sub-agents.md |
Agent validation |
skills.md |
Skill validation |
hooks.md |
Hook validation |
hooks-guide.md |
Hook validation (patterns) |
plugins-reference.md |
Plugin config validation |
plugins/marketplace-reference.md |
Marketplace config validation |
plugins/dependencies.md |
Plugin dependency validation |
plugins/cli-reference.md, plugins/measure.md, plugin-evals.md |
Tooling opportunities (validate/tag/details/eval) |
plugins.md |
General plugin validation |
settings.md |
Permission mode validation |
mcp.md |
MCP config validation |
If any required cache file is missing: STOP and tell the user to run
bash scripts/fetch-claude-docs.sh first. Do NOT silently skip or attempt to fetch.
Also read .claude/skills/docs-check/references/validation-rules.md and extract the
section relevant to each component type. Each worker gets ONLY its section.
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.
- 21d ago Changed · +2 lines 9709976794a4
- 1mo ago First seen · 209 lines · 70 tokens per session scan A 57675b353492
docs-validation-orchestrator is an agent published in the GitHub repository oliver-kriska/claude-elixir-phoenix (568 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 1,774 once invoked, about $0.0003 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 agents, from other repositories
craft-planner
Breaks large Craft CMS plugin or module work into feature-by-feature implementation steps, each with layers, tests, and a runnable verification gate, and can research how core or public plugins solve the same problem. Read-only; returns the plan for the caller to save. Use before craft-feature-builder on anything with…
craft-code-reviewer-deep
Deep code review on Opus for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Read-only. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
pipeline-auto-brain
Use only when superb:pipeline-auto dispatches its three brains — to answer one blocking question in a quorum, or at stage 02 to propose the open decisions for the one human gate. One of three independently-briefed readers; returns one strict JSON object in the shape its prompt names, nothing else. Never dispatched by…
bug-investigator
Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.
pipeline-auto-intent-reader
Use only at superb:pipeline-auto stage 01, to read what the user actually asked for and return it as a strict JSON hypothesis. One of three independent readers. Reads and reports; never designs, never proposes, never chooses a stack.
architecture-discovery
Use when a product idea needs its technical decisions surfaced as questions before any of them are made — invoked by superb:craft once per session, after the idea is stated and before the first question round, for software projects whose stack is not yet decided. Returns candidate questions only; never chooses a stack…