Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pwdev-solucoes/pwdev-claude-marketplace/plugin install pwdev-codeWrote 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/commands/pwdev-solucoes/pwdev-claude-marketplace/verify)<a href="https://agentmods.dev/commands/pwdev-solucoes/pwdev-claude-marketplace/verify"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/verify/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/commands/pwdev-solucoes/pwdev-claude-marketplace/verify"><img src="https://agentmods.dev/badge/commands/pwdev-solucoes/pwdev-claude-marketplace/verify.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.00010 | $0.01221 |
| Opus 5 | $0.00005 | $0.00611 |
| Sonnet 5 | $0.00002 | $0.00244 |
| Haiku 4.5 | $0.00001 | $0.00122 |
Grade A, and why
verify 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.
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pwdev-code:verify — Verification Phase
Role (orchestrator — the verifier subagent does the work, adversarially)
The verifier's goal is to REFUTE that the phase is complete, not confirm it. It re-runs evidence itself and distrusts execution summaries.
Entry Gate
ls .planning/phases/*/execution/*-summary.md >/dev/null 2>&1 || { echo "❌ No summaries. Run /pwdev-code:execute first."; exit 1; }
If .planning/state.md contains review_gate: BLOCKED → abort:
❌ Review gate is BLOCKED (critical findings open).
Fix them via /pwdev-code:execute + /pwdev-code:review, or explicitly override.
Recommended: run /pwdev-code:review before verify — its reports feed
the verifier (unresolved critical/high findings count as DoD failures).
Flow
STEP 0 — Language
Follow ${CLAUDE_PLUGIN_ROOT}/references/language.md (resolve lang from
.planning/config.json; ask only if unset).
STEP 1 — Gather Spawn Inputs
Read (for the prompt only): CLAUDE.md (section 11 — Verification,
Goal-Backward), spec.md sections 2, 3, 5, 6, 7, 8 (full text), paths of
execution/*-summary.md, paths of review/code-review.md and
review/qa-report.md (if they exist), active skills list, and a RELEVANT
MEMORY block per ${CLAUDE_PLUGIN_ROOT}/references/memory.md (lessons
first). Project verification commands come from CLAUDE.md sections 12 and 14.
STEP 2 — Spawn the Verifier (real subagent)
Normal mode — one Task call:
subagent_type:pwdev-code:verifiermodel: resolve per${CLAUDE_PLUGIN_ROOT}/references/model-profiles.md- prompt: follow the verifier template in
${CLAUDE_PLUGIN_ROOT}/references/spawn-contracts.md— full spec sections, summary paths (to be distrusted), review report paths,LANGUAGE: {lang}, and the goal: refute completion. - Log the resolved model right after spawning:
"${CLAUDE_PLUGIN_ROOT}/scripts/audit-log.sh" spawn verify VERIFY pwdev-code:verifier <model>
It writes verify/verify.md (+ verify/fix-{NN}.md if rejected) and replies
with ≤10 lines.
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 · 103 lines · 10 tokens per session scan A 6a6dd07f045d
verify is a command published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 2d ago), licensed Apache-2.0. It adds 10 tokens to every session and 1,221 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.