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/dasdigitalemomentum/opencode-processing-skills/author-and-verify-implementation-plannpx skills add DasDigitaleMomentum/opencode-processing-skills --skill author-and-verify-implementation-plangit clone --depth 1 https://github.com/DasDigitaleMomentum/opencode-processing-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/dasdigitalemomentum/opencode-processing-skills/author-and-verify-implementation-plan)<a href="https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/author-and-verify-implementation-plan"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/author-and-verify-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.00033 | $0.02134 |
| Opus 5 | $0.00016 | $0.01067 |
| Sonnet 5 | $0.00007 | $0.00427 |
| Haiku 4.5 | $0.00003 | $0.00213 |
Grade A, and why
author-and-verify-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 6d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Author and Verify Implementation Plan
This skill standardizes the second pass between planning and execution:
- It authors or refines
plans/<plan>/implementation/phase-N-impl.md - It verifies the plan against the current source code (and uses
docs/**inventories when present)
This skill exists to prevent “hand-wavy” implementation plans and reduce drift between phase intent and repo reality.
When to Use
Use this skill when:
- The phase is already gated (scope/DoD decided in
plan.md+phases/phase-N.md). - You want the “how” (
implementation/phase-N-impl.md) to be grounded in current code. - You plan to delegate execution later via
execute-work-package.
Do not use this skill to:
- Change the gated phase intent/scope (that is primary work via
update-plan). - Generate documentation (use
generate-docs/update-docs).
Execution Model
Roles
-
Primary (maintainer)
- Owns phase gating and decisions.
- Delegates authoring/verification of the implementation plan when helpful.
- Reviews the resulting implementation plan for scope compliance.
-
Subagent (delegate or justified model alias)
- Uses one fresh Delegate session for exactly one phase implementation plan.
- Reads: phase + existing implementation plan (if any) + relevant docs + relevant code.
- Writes:
plans/**/implementation/phase-N-impl.md.
Routing Matrix (Who does what)
- Writes:
plans/<plan>/implementation/phase-N-impl.md(authoring/refinement grounded against current code). - Does NOT write:
plans/<plan>/plan.mdorplans/<plan>/phases/**(phase intent/scope/DoD remain gated by the primary). - Primary: owns phase gating; reviews impl-plan for scope compliance.
- delegate: performs the author+verify pass and writes the impl-plan. Use
delegate-strongonly when phase complexity or risk justifies it. - implementer: not used for plan artifacts in this skill.
Why plans/ and docs/ matter
What ships with it
2 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.
- 6d ago First seen · 158 lines · 33 tokens per session scan A fd0815f8369b
author-and-verify-implementation-plan is a skill published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (58 stars, last pushed 26d ago), licensed MIT. It adds 33 tokens to every session and 2,134 once invoked, about $0.0002 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-30.
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…