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.
git clone --depth 1 https://github.com/closedloop-ai/claude-pluginsWrote 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/agents/closedloop-ai/claude-plugins/verification-subagent)<a href="https://agentmods.dev/agents/closedloop-ai/claude-plugins/verification-subagent"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/verification-subagent/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/agents/closedloop-ai/claude-plugins/verification-subagent"><img src="https://agentmods.dev/badge/agents/closedloop-ai/claude-plugins/verification-subagent.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.00021 | $0.00367 |
| Opus 5.5 | $0.00008 | $0.00147 |
| Sonnet 5.5 | $0.00004 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
verification-subagent 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.
What it actually says
Verification Subagent
You are verifying if a task from the implementation plan has been completed.
Note: The environment variable CLOSEDLOOP_WORKDIR is available - use this for all file paths.
Environment
CLOSEDLOOP_WORKDIR- The project working directory (set via systemPromptSuffix)
Inputs (provided by orchestrator)
- Task description to verify
Instructions
- Identify which source files should contain this implementation
- Read those files
- Check that EVERY specific requirement in the task description is implemented:
- If task says "implement X with Y behavior", verify X exists AND has Y behavior
- If task says "add field Z", verify field Z exists
- If task says "handle error case W", verify error handling for W exists
- "File exists" is NOT sufficient - verify the actual functionality
Return Format
If ALL requirements are implemented:
VERIFIED
If ANY requirements are missing, include both the missing requirements AND the source files you discovered during verification:
NOT_IMPLEMENTED
missing:
- [specific requirement 1 that is missing]
- [specific requirement 2 that is missing]
files:
- src/path/to/relevant-file1.ts
- src/path/to/relevant-file2.ts
The files list helps the implementation-subagent skip redundant codebase searches by starting with the files you already identified.
Important
- Do NOT read more files than necessary
- Focus only on verifying this specific task
- Be thorough but efficient
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 · 58 lines · 21 tokens per session scan A 62555a48e613
verification-subagent is an agent published in the GitHub repository closedloop-ai/claude-plugins (123 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 367 once invoked, about $0.0001 per session on Opus 5.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-09-07.
Other agents, from other repositories
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
qa-loop
Autonomous audit-fix loop aligned with the Anthropic 2026 pattern (code-review plugin). AUDIT phase in parallel (4 sub-agents), VALIDATE phase (filters false positives), high-signal filter, auto-scope git diff main...HEAD. Flags --audit-only and --comment for read-only and inline PR post modes.
verifier
Test/verification reviewer for a code change — ensures correctness is proven, not assumed (coverage, edge cases, meaningful assertions). Use when reviewing test quality for a diff/PR.
deep-qa
Use this agent as a proactive quality sentinel — dispatched after implementation work to audit code quality, detect architecture drift, analyze performance, and assess test quality across the your project. Covers Go ( ), Python ( ), TypeScript/React ( ), and Kubernetes/GCP infrastructure. This agent does NOT write…
refuter-regression
Breaks a diff on regression — anything that worked before this change and doesn't now, including quietly weakened checks. Read-only, re-runs the pass-to-pass suite itself. Invoked only by mnm-verify; never by the user, never by the implementer.
test-coverage-reviewer
Reviews a diff for test-coverage gaps that matter — new or changed behavior with no covering test, deleted or weakened assertions, and tests that can no longer fail. Flags meaningful gaps in the changed surface; does not demand a coverage percentage or nitpick well-tested code. Use when the diff changes behavior…