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 ApexIQ/skillsmith --skill how_to_create_implementation_plangit clone --depth 1 https://github.com/ApexIQ/skillsmithWrote 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/apexiq/skillsmith/how_to_create_implementation_plan)<a href="https://agentmods.dev/skills/apexiq/skillsmith/how_to_create_implementation_plan"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/how_to_create_implementation_plan/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/apexiq/skillsmith/how_to_create_implementation_plan"><img src="https://agentmods.dev/badge/skills/apexiq/skillsmith/how_to_create_implementation_plan.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.00023 | $0.00440 |
| Opus 5 | $0.00012 | $0.00220 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
how-to-create-implementation-plan 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 8d 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.
What it actually says
📝 How to Create an Implementation Plan
Why: A plan is a contract. It prevents "scope creep" and ensures alignment before coding.
1. Structure (The Blueprint)
Every implementation plan should include:
A. Goal & Overview
- Goal: 1-sentence summary (e.g., "Add user authentication").
- Background: Why is this needed? What problem does it solve?
- User Review: Flag breaking changes or significant tech decisions.
B. Proposed Changes
Group by component (Frontend/Backend/Database).
- [NEW] File/component to create.
- [MODIFY] Existing file + bullet points of changes.
- [DELETE] Files to remove.
C. Verification Plan
- Automated Tests: What tests will cover this?
- Manual Testing: Step-by-step "click path" to verify the feature.
D. Risks & Considerations
- What could go wrong?
- Are there alternative approaches?
2. Methodology
- Research First: Understand the existing code before proposing changes.
- Think in Systems: If you add a frontend button, does the backend API exist?
- Keep it Bite-Sized: Plans >3 days of work should be split into phases.
3. Checklist
- Is the goal clearly stated?
- Are all affected files listed?
- Is the verification plan executable?
- Have risks been considered?
Examples
- Good plan: Clear goal, specific file changes, test plan included.
- Bad plan: Vague "refactor backend", no specifics.
Guidelines
- Get plan approved before writing code.
- Update the plan if scope changes during implementation.
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.
- 8d ago First seen · 57 lines · 23 tokens per session scan A 25abae5b1b4c
how-to-create-implementation-plan is a skill published in the GitHub repository ApexIQ/skillsmith (5 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 440 once invoked, about $0.0001 per session on Opus 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-31.
Other skills, from other repositories
pptx
Extract text from Microsoft PowerPoint presentations.
xlsx
Extract data from Excel and CSV files.
agent-teams
Multi-agent team orchestration with native Agent Teams. Trigger when the user wants to launch a team of agents, coordinate parallel work with inter-agent communication, or use swarm mode.
ops-infra-code
Infrastructure as Code with Terraform/OpenTofu. Trigger to create modules, configure backends, write idiomatic HCL, or audit infrastructure.
Read, create and manipulate PDF files — extract text and tables, merge, split, rotate, reorder and delete pages, read and fill AcroForm fields, add or strip metadata, encrypt and decrypt, and generate new PDFs from HTML or from scratch. Also covers rasterising pages to images so a PDF can actually be looked at, and…
easd-verify
Run the final EASD integration and evidence gate against accepted AC policies, then prepare a convergence recommendation. Use after implementation and any required independent review; not for task-local code review or ordinary tests outside EASD.