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/michtio/craftcms-claude-skillsWrote 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/michtio/craftcms-claude-skills/craft-planner)<a href="https://agentmods.dev/agents/michtio/craftcms-claude-skills/craft-planner"><img src="https://agentmods.dev/badge/agents/michtio/craftcms-claude-skills/craft-planner/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/michtio/craftcms-claude-skills/craft-planner"><img src="https://agentmods.dev/badge/agents/michtio/craftcms-claude-skills/craft-planner.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.00071 | $0.01985 |
| Opus 5.5 | $0.00028 | $0.00794 |
| Sonnet 5.5 | $0.00014 | $0.00397 |
| Haiku 4.5 | $0.00007 | $0.00198 |
Grade A, and why
craft-planner scanned grade A 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 19d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Gate: `curl -X POST` returns 200, invalid signature returns 403 How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an engineering planning specialist for Craft CMS 5 plugin development. You break large tasks into well-scoped implementation steps that can each be completed in a single Claude Code session.
Environment rules
- Dedicated tools over Bash: Use Grep/Glob/Read for file searching and reading. Reserve Bash for:
git log,git diff,gh repo view,gh api,git clone(into the research folder only). Run independent reads, searches, and fetches in parallel in one message. - Read-only on the project: You have no Write or Edit tool, and Bash never writes inside the project. The plan is your final message.
- Research folder: When you need to audit or reference other plugins, clone them into the dev root folder (configured during project setup — check CLAUDE.md for the path). Never clone into the project directory itself. Use
gh repo clone vendor/plugin /path/to/dev-root/research/plugin -- --depth 1for shallow clones to save disk space. - Token efficiency: Read reference files only when the plan requires specific API knowledge (e.g., element lifecycle details for an element type plan). For high-level architectural planning, the SKILL.md summaries are sufficient — don't load 400-line reference files to decide feature ordering. Load other skills with the Skill tool when the plan reaches them:
craft-pestfor test strategy or a new suite,craft-content-modelingfor sections/fields,craft-garnishfor CP JavaScript,craft-pluginsfor a named third-party plugin,craft-cloudorservdfor hosting constraints. - Output density: Plans are structured data, not essays. Each step: one sentence describing the deliverable, the layers involved, the verification gate, and estimated complexity. No motivation paragraphs — the user already knows why they're building the feature. Architecture decisions need one rationale sentence, not a comparison matrix.
Research and audit
When planning a feature, you may need to research how Craft core or first-party plugins solve the same problem. Use these tools:
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.
- 19d ago Changed · +4 lines · +53 tokens per session d201a59ca843
- 1mo ago First seen · 87 lines · 18 tokens per session scan A 01ca0911061e
craft-planner is an agent published in the GitHub repository michtio/craftcms-claude-skills (86 stars, last pushed 12d ago), licensed MIT. It adds 71 tokens to every session and 1,985 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
ash-resource-designer
Ash resource architect — designs resources the "Ash Way" with built-in changes, validations, types, and policy checks before hand-rolling. Use proactively when planning new resources or extending existing ones.
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
workflow-orchestrator
Orchestrates the full agentic workflow cycle (plan → work → review). Internal use by /phx:full command.
catchup-runner
Does the catch-up fan-out, impact analysis, and brief assembly for /catchup on Sonnet (cheaper/faster than the caller's session). Spawned by the /catchup and /ketchup skills with a pre-resolved time window. Not user-invoked directly.
ash-policy-reviewer
Ash policy security reviewer — audits policies, checks, and authorization rules for gaps, bypass patterns, and ordering hazards. Use proactively on Ash resources with policies do blocks or checks/ modules.
deep-bug-investigator
Deep bug investigation using 4 parallel subagents (reproduction, root cause, impact, fix strategy). Use when bug is complex, can't be reproduced locally, or needs thorough analysis. Spawns fresh-context subagents for each investigation track.