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/dcostenco/prism-coder/verification-plannernpx skills add dcostenco/prism-coder --skill verification-plannergit clone --depth 1 https://github.com/dcostenco/prism-coderWrote 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/dcostenco/prism-coder/verification-planner)<a href="https://agentmods.dev/skills/dcostenco/prism-coder/verification-planner"><img src="https://agentmods.dev/badge/skills/dcostenco/prism-coder/verification-planner.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 | $0.00044 | $0.00341 |
| Opus 5 | $0.00022 | $0.00170 |
| Sonnet 5 | $0.00009 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
Verification Planner 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 4d 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
Verification Planner (v7.2.0)
You MUST use this skill when generating an implementation_plan.md. You are required to create a test_assertions.json file in the project root to guide the automated Verification Runner.
🚀 Workflow
- Plan: Alongside your MD plan, define assertions in
test_assertions.json. - Define Layers: Categorize tests into
data(schema),pipeline(files/APIs), oragent(logic). - Set Severity:
warn: Non-blocking logs.gate: Blocks progression on failure.abort: Stops the pipeline immediately (safety-critical).
🛠️ Assertion Types
sqlite_query: Validate DB state.http_status: Verify API health.file_exists/file_contains: Check filesystem.quickjs_eval: Sandbox JS logic for complex checks.
🧠 Claw-as-Validator
If PRISM_VERIFICATION_HARNESS_ENABLED=true, delegate your JSON suite to the local Claw agent for adversarial review before execution to catch missing coverage or false positives.
🔗 References
- EXAMPLES.json: Full JSON schema and multi-layer example.
- CONFIG.md: Environment variables and severity guidelines.
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.
- 4d ago First seen · 31 lines · 44 tokens per session scan A aff43d4764c4
Verification Planner is a skill published in the GitHub repository dcostenco/prism-coder (157 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 341 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
typescript-lsp
Search TypeScript SYMBOLS (functions, types, classes) - NOT text. Use Glob to find files, Grep for text search, LSP for symbol search. Provides type-aware results that understand imports, exports, and relationships.
business-model-validator
Use when a prospect, new customer, or existing operator wants to know whether Zooza fits their business, or which Zooza features map to how they operate. No Zooza account required — works as a pure knowledge interview.
class-management
Use when the user wants to create a new class, group, or course in Zooza — e.g. "set up a Monday yoga class", "add a new group", "schedule a course". Guides through programme selection, venue, trainer, session pattern, and commits.
feedback-nudge
Use when the user wants to report a bug, request a feature, or send feedback to the Zooza engineering team. Also offer proactively after a successful commit operation (max once per week).
negotiate-terminology
Use when the user wants to set up their business vocabulary — what they call programmes, classes, sessions, trainers. Also use when the user says "you're using the wrong words" or this is their first session with Zooza MCP.
gw1-build-assistant
Use when the user asks about Guild Wars 1 (the original 2005 game, not GW2) — designing or reviewing skill bars, decoding or producing template codes (strings like "OgCjkurIrSuXaXPXBYihygvlYcA"), hero team composition, skill lookups or comparisons, or pasting a paw-ned2 team blob ("pwnd0001..."). Use the gw1-mcp tools…