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 AlteredCraft/claude-code-plugins --skill implementation-plan-creatorgit clone --depth 1 https://github.com/AlteredCraft/claude-code-pluginsWrote 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/alteredcraft/claude-code-plugins/implementation-plan-creator)<a href="https://agentmods.dev/skills/alteredcraft/claude-code-plugins/implementation-plan-creator"><img src="https://agentmods.dev/badge/skills/alteredcraft/claude-code-plugins/implementation-plan-creator/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/alteredcraft/claude-code-plugins/implementation-plan-creator"><img src="https://agentmods.dev/badge/skills/alteredcraft/claude-code-plugins/implementation-plan-creator.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.00015 | $0.00631 |
| Opus 5.5 | $0.00006 | $0.00252 |
| Sonnet 5.5 | $0.00003 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
Grade A, and why
implementation-plan-creator 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 2mo 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are creating the Implementation Plan artifact (implementation-plan.md) for an artifact-driven development workflow.
Input Context
- Read
.artifacts/bld-<project-slug>/todo.mdfor the approved task list - Reference the conversation context for requirements and constraints
Your Task
Create .artifacts/bld-<project-slug>/implementation-plan.md.
Plan Structure
Project Summary
One paragraph describing what's being built and its core purpose.
User Review Required
Surface decisions requiring user input prominently at the top. Use blockquote callouts:
IMPORTANT Technology Stack: The plan uses X with Y. If you prefer Z, please let me know.
IMPORTANT [Decision Topic]: The proposed approach uses [approach]. Alternative approaches include:
- Alternative 1
- Alternative 2
- Alternative 3
Please confirm the preferred approach.
This section ensures approval gates are visible, not buried.
Proposed Changes
Organize by logical layer or area (Backend Service Layer, Frontend Components, Configuration, etc.).
For each file:
[NEW] path/to/file.ext
Brief description of this file's purpose:
- Responsibility one
- Responsibility two
- Responsibility three
[MODIFY] path/to/existing.ext
Changes to make:
- Add X functionality
- Update Y to support Z
Testing Strategy
How the implementation will be verified. Keep it practical—what tests or checks prove it works.
Artifact Structure
---
status: pending
created: <timestamp>
updated: <timestamp>
---
# <Project Name>
<One paragraph project summary>
## User Review Required
> **IMPORTANT**
> **[Decision 1]**: ...
> **IMPORTANT**
> **[Decision 2]**: ...
## Proposed Changes
### <Layer/Area Name>
**[NEW]** `filename.ext`
Description:
- Point one
- Point two
**[MODIFY]** `filename.ext`
Changes:
- Change one
- Change two
### Testing Strategy
...
After Creation
Present the artifact to the user. This is an approval gate.
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.
- 2mo ago First seen · 117 lines · 15 tokens per session scan A 1c29bc9767e7
implementation-plan-creator is a skill published in the GitHub repository AlteredCraft/claude-code-plugins (12 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 631 once invoked, about $0.0001 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…