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 The-Artificer-of-Ciphers-LLC/skills-from-the-artificer --skill adr-phase-coveragegit clone --depth 1 https://github.com/The-Artificer-of-Ciphers-LLC/skills-from-the-artificerWrote 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/the-artificer-of-ciphers-llc/skills-from-the-artificer/adr-phase-coverage)<a href="https://agentmods.dev/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/adr-phase-coverage"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/adr-phase-coverage/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/the-artificer-of-ciphers-llc/skills-from-the-artificer/adr-phase-coverage"><img src="https://agentmods.dev/badge/skills/the-artificer-of-ciphers-llc/skills-from-the-artificer/adr-phase-coverage.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.00176 | $0.01870 |
| Opus 5.5 | $0.00070 | $0.00748 |
| Sonnet 5.5 | $0.00035 | $0.00374 |
| Haiku 4.5 | $0.00018 | $0.00187 |
Grade A, and why
adr-phase-coverage 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 12d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADR phase coverage: nothing falls between phases
Why this exists
When a design document is sliced into implementation phases, the failure mode is rarely a phase
doing its job badly — it is a deliverable that is nobody's job. Each phase has locally-coherent
acceptance criteria, so each can honestly call itself "done," while a cross-cutting deliverable falls
into the seam between two phase boundaries. The classic shape: Phase 4 builds the library and says
"the user-facing command lands in Phase 5"; Phase 5's actual scope is something else; the command is
now owned by no one — and the docs cheerfully describe it as shipping. (A real case study is in
references/anti-patterns.md.)
This skill makes that gap mechanically visible before the plan is locked. You extract a small trace of decisions↔phases; a deterministic checker does the exhaustive cross-referencing humans get wrong. It is language-, framework-, and process-agnostic — it reads your decisions and your phases, whatever form they take.
The deep "why" — requirements traceability, walking skeletons, vertical slicing, the horizontal-
layering trap — is in references/methodology.md (with citations). You don't need it to run the check.
The four gaps it catches
- Orphaned decision — an ADR decision owned by no phase.
- Dangling deferral — Phase N says "handled in Phase M," but Phase M neither owns nor accepts it. The hand-off points into the void.
- Multi-owner ambiguity — two phases both claim a decision; confirm it's a deliberate split, not two phases each assuming the other does it.
- Keystone unwired — a user-facing capability (a command/route/UI the user invokes) is owned, but no owning phase's acceptance criteria wire a user-reachable surface. A library can be fully built and still be unreachable; this forces an explicit "user can invoke X" acceptance.
Workflow
Do this when decomposing a design into phases, or to audit an existing decomposition.
What ships with it
10 files 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.
- assets/trace.adr1244-broken.json 2.0 KB
- assets/trace.example.json 2.4 KB
- evals/evals.json 3.0 KB
- evals/fixtures/adr-0007-apikeys.md 1.1 KB
- evals/fixtures/ROADMAP-apikeys.md 893 B
- evals/trigger-eval.json 3.7 KB
- references/adapting-to-your-repo.md 4.6 KB
- references/anti-patterns.md 5.1 KB
- references/methodology.md 5.4 KB
- scripts/check_coverage.py 11 KB runs code
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.
- 12d ago First seen · 134 lines · 176 tokens per session scan A 5b874d72b6f5
adr-phase-coverage is a skill published in the GitHub repository The-Artificer-of-Ciphers-LLC/skills-from-the-artificer (6 stars, last pushed yesterday), licensed MIT. It adds 176 tokens to every session and 1,870 once invoked, about $0.0007 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-15.
Other skills, from other repositories
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…
incident-postmortem
Escribe un postmortem de incidente estructurado o revisión post-incidente. Úsalo cuando se te pida escribir un postmortem, reporte de incidente, revisión P1/P2, reporte de apagón o RCA (análisis de causa raíz). Produce un postmortem sin culpables con cronología, causa raíz, factores contribuyentes, resumen de impacto…
stakeholder-update
Crear actualizaciones ejecutivas concisas para stakeholders usando el framework BLUF (Bottom Line Up Front). Usa cuando te pidan escribir una actualización de estado, reporte de progreso, comunicación de proyecto o briefing ejecutivo para liderazgo o stakeholders. Produce una actualización encabezada por BLUF con…
technical-debt-register
Documenta y prioriza un backlog de deuda técnica con impacto empresarial, estimaciones de esfuerzo y estrategia de resolución. Úsalo cuando se te pida auditar deuda técnica, crear un registro de deuda, priorizar deuda técnica para un trimestre, documentar atajos arquitectónicos o construir una hoja de ruta de…
cs-health-scorecard
Construir un cuadro de mando de salud del cliente para una cuenta específica. Úsalo cuando te pidan calificar la salud de la cuenta, evaluar el riesgo de renovación, construir un panel de salud o evaluar la probabilidad de que una cuenta se renueve o expanda. Produce un cuadro de mando de salud estructurado con estado…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…