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 startgit 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/start)<a href="https://agentmods.dev/skills/oliver-kriska/claude-elixir-phoenix/start"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/start/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/start"><img src="https://agentmods.dev/badge/skills/oliver-kriska/claude-elixir-phoenix/start.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.00057 | $0.01768 |
| Opus 5.5 | $0.00023 | $0.00707 |
| Sonnet 5.5 | $0.00011 | $0.00354 |
| Haiku 4.5 | $0.00006 | $0.00177 |
Grade A, and why
start 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 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.
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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rewrite Start — Entry, Resume, Status
The front door of the rewrite workflow. It explains the method once, finds where an existing rewrite stands, checks that the legacy source has not changed underneath it, and routes to the next phase.
/rewrite:start → /rewrite:analyze → /rewrite:architect → /rewrite:roadmap
↓ per slice
/rewrite:verify ← /phx:work ← /phx:plan
Iron Laws
- ONE PHASE AT A TIME — route to the next phase; with
--auto, chain only analyze → architect → roadmap - IDENTITY BEFORE RESUME — compare the source snapshot before trusting earlier artifacts
- STATE COMES FROM FILES — read
.claude/rewrite/and the ledger script, never memory of a previous session --autoSTOPS AT DECISIONS — it never approves ASSUMED choices, never starts/phx:work, never deploys or touches production data- LEGACY STAYS READ-ONLY — never write into or execute the source app
Workflow
1. Check dependencies and detect state
If the phx:plan skill is not in this session's skill list, tell the user to
install elixir-phoenix from the marketplace that provided rewrite
(/plugin install elixir-phoenix@oliver-kriska, or that marketplace's
name), then run /reload-plugins. Without it the architect consults and
the /phx:plan handoff fail, so --auto stops after analyze.
ls .claude/rewrite/ .claude/rewrite/architecture/ 2>/dev/null && sed -n '1,40p' .claude/rewrite/status.md
python3 "${CLAUDE_SKILL_DIR}/../architect/scripts/ledger.py" check --rewrite-dir .claude/rewrite # once architecture.md exists
Read the first matching row, top to bottom. An active slice comes before seeding a new one:
| Found | State | Next |
|---|---|---|
| nothing | new | step 2, then /rewrite:analyze <path> |
phase analyzing, or an analysis/*.md missing |
analyze incomplete | /rewrite:analyze <Source path> |
analysis/*.md, no ADR-000 |
analyzed | /rewrite:architect |
ADR-000, no architecture.md |
architect incomplete | /rewrite:architect (resumes at step 4) |
ADR-000 + architecture.md, but decisions.md or divergences.md missing, phase architecting, or ledger.py check fails |
architect incomplete | /rewrite:architect (resumes at step 4 or 5) |
ADR-000 + architecture.md + decisions.md + divergences.md, clean ledger, no roadmap.md |
architected | /rewrite:roadmap |
a slice planned or in-progress whose plan.md has at least one - [x] and no - [ ] |
awaiting gate | /rewrite:verify NN |
a slice planned or in-progress |
building | /phx:work .claude/plans/{slug}/plan.md, then /rewrite:verify NN |
roadmap.md with ready or seeded slices |
slicing | /rewrite:roadmap --next |
every slice done |
complete | release rehearsal slice, or close out |
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 · 131 lines · 57 tokens per session scan A bc925138c05f
start is a skill published in the GitHub repository oliver-kriska/claude-elixir-phoenix (567 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,768 once invoked, about $0.0002 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-17.
Other skills, from other repositories
socratic-review
Socratic code review and refactoring session — whether it's your own code, a teammate's PR, or something you inherited. Leads you to see the issues through questions, names smells and moves precisely, then closes with a concrete plan.
prior-art
Discover how a codebase already handles a specific concern — search broadly, find every instance, and assess consistency. The "how does this app do X?" tool.
fable-super-audit
Comprehensive, rubric-driven, whole-repository code audit that ends in a prioritized improvement plan with an executive health grade. Built to run in a premium, time-limited model session (Fable): it dispatches cheaper Opus/Sonnet subagents to explore the codebase and pre-build a project-tailored audit checklist, then…
elderly-ui-audit
A code review for making websites and mobile apps easier for older people to use, based on Chinese government accessibility guidelines.
odoo-code-review
Use when reviewing Odoo code — yours before commit, Claude's after generation, or a teammate's PSDU PR. Catches shape-of-bad-code issues that lint won't, plus customer-readiness gaps. Invoke before claiming Odoo work is done.
odoo-code-review
Use when reviewing Odoo code — yours before commit, Claude's after generation, or a teammate's PSDU PR. Catches shape-of-bad-code issues that lint won't, plus customer-readiness gaps. Invoke before claiming Odoo work is done.