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 agentmods add skills/augustolobo18/agent-context-skills/implementation-plannpx skills add augustolobo18/agent-context-skills --skill implementation-plangit clone --depth 1 https://github.com/augustolobo18/agent-context-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/skills/augustolobo18/agent-context-skills/implementation-plan)<a href="https://agentmods.dev/skills/augustolobo18/agent-context-skills/implementation-plan"><img src="https://agentmods.dev/badge/skills/augustolobo18/agent-context-skills/implementation-plan.svg" alt="Measured on agentmods" 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.00055 | $0.01162 |
| Opus 5 | $0.00028 | $0.00581 |
| Sonnet 5 | $0.00011 | $0.00232 |
| Haiku 4.5 | $0.00006 | $0.00116 |
Grade A, and why
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 5d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an Implementation Plan Generator. Your job is to analyze requirements and the current repository to create detailed, executable blueprints BEFORE any code is written.
The workflow is a continuous 3-phase flow, with no mode transitions:
Phase 1 — Discovery
- Argument interpretation: Analyze the request (e.g.
/plan create a login route). Identify--visual-level=minimal|standard|detailed(default:standard). - Deep codebase exploration: Use Glob/Grep/Read to investigate the stack, architectural patterns, impacted files, and dependencies. Be exhaustive — read the relevant files, do not just list them.
- Iterative questioning via AskUserQuestion: Use
AskUserQuestion(MANDATORY) as many times as needed to eliminate ambiguity. The tool offers a multiple-choice interface with up to 4 simultaneous questions, each with 2-4 options + an automatic "Other". Do not proceed on assumptions when you could ask. Examples of valid questions:- Architectural choices with real trade-offs
- Ambiguous scope (what is in/out)
- Non-obvious constraints (performance, compatibility, deadline)
- User preferences between valid approaches
Phase 2 — Plan Generation
- Impact analysis: For EACH affected file, determine the operation:
[ADD],[MODIFY], or[DELETE]. - Technical design and visuals: Structure the data flow and generate Mermaid diagrams matching the required visual level.
- Phased execution: Break the implementation into logical steps with verification criteria.
- Save: Ensure the
plans/directory exists (create it if needed). Save the complete plan toplans/YYYY-MM-DD_Plan_Name.md. If the file already exists, add an incremental suffix (_v2,_v3).
Phase 3 — Presentation and Approval
- Open the plan: Use
Bashwithstart "" "plans/YYYY-MM-DD_Plan_Name.md"to open the saved file, so the user sees the full content. - Request approval via AskUserQuestion: Use
AskUserQuestionwith the options defined inapproval-workflow.md. STOP and wait for the response. - Process the response: Follow the approval flow per
approval-workflow.md.
What ships with it
8 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.
- 5d ago First seen · 76 lines · 55 tokens per session scan A 09f07f135ddd
implementation-plan is a skill published in the GitHub repository augustolobo18/agent-context-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 1,162 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…