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 oliver-kriska/claude-elixir-phoenix --skill roadmapgit 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/skills/oliver-kriska/claude-elixir-phoenix/roadmap)<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/roadmap"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/roadmap/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/oliver-kriska/claude-elixir-phoenix/roadmap"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/roadmap.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.00045 | $0.02383 |
| Opus 5.5 | $0.00018 | $0.00953 |
| Sonnet 5.5 | $0.00009 | $0.00477 |
| Haiku 4.5 | $0.00005 | $0.00238 |
Grade B, and why
roadmap scanned grade B with 1 finding 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 today.
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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -n "pending" .claude/rewrite/architecture/divergences.md How it starts
The opening of the file, as written. The whole thing — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rewrite Roadmap — Slices and phx Handoff
Phase 3. Cut the accepted architecture into vertical slices that each
prove capabilities end to end, then hand one slice at a time to the phx
workflow. The handoff is a file contract: interview.md that /phx:plan
already consumes, plus a scratchpad seed. phx is not modified.
/rewrite:architect → /rewrite:roadmap <-- YOU ARE HERE
↓ interview.md + scratchpad.md
/phx:plan → /phx:work → /rewrite:verify → /rewrite:roadmap --next
Iron Laws
- SLICES ARE CAPABILITIES — each slice delivers user, operator or machine goals end to end, never "all models" or "all controllers"
- RISK FIRST — the first product slice is the riskiest core capability, after a foundation slice
- NO FABRICATED INTERVIEW — the seed says it was generated, keeps ASSUMED and UNDECIDED visible, and has no invented transcript
- COMPLETE ONLY WHEN EARNED — every coverage dimension ≥1, total ≥8, no UNDECIDED row and no unresolved consequential decision in the slice
- NEVER OVERWRITE USER WORK — check an existing plan directory before writing; never hand phx any file but the slice's own
interview.md - NO HANDOFF ON UNRESOLVED DECISIONS — never invoke
/phx:planwhile a consequential decision for the slice is ASSUMED, proposed or pending - phx OWNS APPROVAL —
/phx:planstops for approval; never auto-start/phx:work
Workflow
1. Preconditions
Require ADR-000 with Status accepted or ASSUMED, architecture.md and a
clean ledger:
python3 "${CLAUDE_SKILL_DIR}/../architect/scripts/ledger.py" check --rewrite-dir .claude/rewrite
If the check fails, stop and suggest /rewrite:architect.
2. Build or update roadmap.md
Skip to step 3 with --next or --slice when roadmap.md already exists.
Otherwise read ${CLAUDE_SKILL_DIR}/references/slicing.md and write
.claude/rewrite/roadmap.md in this conversation (a delegated writer is a
general-purpose agent with model: "sonnet"), in this order:
What ships with it
2 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.
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.
- today First seen · 183 lines · 45 tokens per session scan B c823b5c3ca25
roadmap is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (567 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 2,383 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-17.
Other skills, from other repositories
craft-content-modeling
Craft CMS 5 content modeling — sections, entry types, fields, Matrix, relations, project config, and content architecture strategy. Covers choosing section types, designing entry types and field layouts, selecting field types, configuring Matrix and nested entries, relations and eager loading, and multi-site…
craftcms
Craft CMS 5 plugin and module development — extending Craft with PHP. Covers elements, element queries, services, models, records, controllers, migrations, queue jobs, console commands, field types, native fields, events, behaviors, Twig extensions, widgets, filesystems, permissions, project config, GraphQL, testing…
craft-php-guidelines
Craft CMS 5 PHP coding standards and conventions. ALWAYS load when writing, editing, reviewing, or discussing any PHP in a Craft plugin or module — even small edits. Also when running ECS, PHPStan, or scaffolding with ddev craft make. Covers: PHPDoc blocks (@author, @since, @throws chains), section headers…
craft-twig-guidelines
Twig coding standards and conventions for Craft CMS 5 templates. ALWAYS load this skill when writing, editing, or reviewing any .twig file in a Craft CMS project — even for small edits. Covers: variable naming (camelCase, no abbreviations), null handling (?? operator, ??? with empty-coalesce plugin), whitespace…
craft-pest
Testing Craft CMS 5 plugins and modules with Pest — test isolation, database safety, and the markhuot/craft-pest-core harness. ALWAYS load when writing, running, fixing, or reviewing tests for a Craft plugin or module, and whenever a suite touches a real Craft install. Covers why rollback is opt-in, tests/Pest.php +…
craft-plugin-release
Releasing Craft CMS plugins — tagging, Packagist propagation, GitHub releases, branch promotion, shared-library ordering, history rewrites. ALWAYS load when cutting, preparing, verifying, or debugging a plugin release: bumping a version, dating a changelog, creating or moving a git tag, or checking what Packagist…