Borrowing it
Nothing to install: this file belongs to mazumba/opencode-dockerized. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mazumba/opencode-dockerized/main/.opencode/config/skills/verification-planning/SKILL.mdgit clone --depth 1 https://github.com/mazumba/opencode-dockerizedWrote 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/mazumba/opencode-dockerized/verification-planning)<a href="https://agentmods.dev/skills/mazumba/opencode-dockerized/verification-planning"><img src="https://agentmods.dev/badge/skills/mazumba/opencode-dockerized/verification-planning/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/mazumba/opencode-dockerized/verification-planning"><img src="https://agentmods.dev/badge/skills/mazumba/opencode-dockerized/verification-planning.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.00043 | $0.00887 |
| Opus 5.5 | $0.00017 | $0.00355 |
| Sonnet 5.5 | $0.00009 | $0.00177 |
| Haiku 4.5 | $0.00004 | $0.00089 |
Grade A, and why
verification-planning 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 1mo 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.
This is a copy
100% identical to verification-planning — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Planning
Build an evidence path
Before changing a non-trivial system, build an evidence path: a project-specific route from the claim being made to evidence that can establish, limit, or refute it.
The purpose is not to select a familiar technique. The purpose is to decide how this system can reveal the truth of this particular change.
1. Frame the claim
State the behavior that needs to become true and the conditions that could make a confident conclusion wrong.
Consider what must change, what must remain true, where the behavior crosses a boundary, and which failure would matter most.
Complete when: the claim, its meaningful uncertainty, and its important failure modes are concrete enough to investigate.
2. Design the evidence path
Derive possible evidence paths from the system itself: its controllable inputs, observable effects, state transitions, invariants, boundaries, artifacts, and ability to repeat or reverse a scenario.
Generate alternatives before choosing. Prefer the path that produces a trustworthy conclusion with proportionate cost, safety, and effort.
Complete when: there is a preferred path, its limitations are understood, and a weaker or stronger alternative is available if circumstances change.
Set a verification budget
At the final state, state the distinct claims, assign one owner to establish or refute each, and choose the minimum non-duplicative evidence that covers the claims and important boundaries. Reuse evidence only while its relevant code, inputs, environment, and state remain valid. Required repository and release checks still apply; broaden or repeat verification only when a stated condition justifies it.
3. Create a verification affordance when needed
When the existing system leaves the decisive truth too indirect or ambiguous, extend the evidence path with a verification affordance: the smallest capability that makes the relevant state controllable, observable, repeatable, and diagnosable for an agent.
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.
- 1mo ago First seen · 112 lines · 43 tokens per session scan A 7d2f4db38901
verification-planning is a skill published in the GitHub repository mazumba/opencode-dockerized (6 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 887 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to verification-planning, differing in 4 lines, and is treated as a copy.
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…
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.