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 skills add mnzralee/claude-multi-agent-architecture --skill verification-before-completiongit clone --depth 1 https://github.com/mnzralee/claude-multi-agent-architectureWrote 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/mnzralee/claude-multi-agent-architecture/verification-before-completion)<a href="https://agentmods.dev/skills/mnzralee/claude-multi-agent-architecture/verification-before-completion"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/verification-before-completion/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/mnzralee/claude-multi-agent-architecture/verification-before-completion"><img src="https://agentmods.dev/badge/skills/mnzralee/claude-multi-agent-architecture/verification-before-completion.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.00025 | $0.01289 |
| Opus 5 | $0.00013 | $0.00645 |
| Sonnet 5 | $0.00005 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
verification-before-completion scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:<PORT>/health How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verification Before Completion Skill
Never mark a task as complete without thorough verification. This skill ensures quality gates are passed before any agent reports success upward. The commands below assume a TypeScript/Node monorepo with Vitest or Jest; the discipline is stack-agnostic and every level maps cleanly onto any compiled language or test runner.
When to Use This Skill
Use this skill:
- Before marking any work package as COMPLETE
- Before committing code changes
- Before reporting success to a supervisor or orchestrator agent
- Before moving to the next task
The Verification Protocol
Level 1: Compilation Verification
# TypeScript compilation
npx tsc --noEmit
# Schema tool generation (if the data model changed)
# [CUSTOMIZE: replace with your ORM or codegen command, e.g. prisma generate, drizzle-kit generate, graphql-codegen]
<your-schema-tool> generate
# Service-specific build
npm run build --workspace=apps/<service-name>
Pass Criteria:
- Zero TypeScript errors (or zero compiler errors in your language)
- Zero schema-generation errors
- Build completes successfully
Level 2: Static Analysis
# Linting
npm run lint
# Type coverage (if configured)
npm run type-coverage
Pass Criteria:
- No new linting errors introduced
- Type coverage maintained or improved
Level 3: Unit Tests
# Run unit tests for affected files
npm test -- --testPathPattern="<affected_file>"
# Run full service tests
npm test -- --projects=<service-name>
Pass Criteria:
- All existing tests pass
- New tests added for new functionality
- No test regressions
Level 4: Integration Verification
# Start service locally
npm run start:dev --workspace=apps/<service-name>
# Health check
curl http://localhost:<PORT>/health
Pass Criteria:
- Service starts without errors
- Health check returns 200 OK
- No runtime errors in logs
Level 5: Functional Verification
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.
- 9d ago First seen · 232 lines · 25 tokens per session scan A 12f12b1450ce
verification-before-completion is a skill published in the GitHub repository mnzralee/claude-multi-agent-architecture (6 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 1,289 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
testing
Test generation, coverage analysis, and test strategy.
mcp-app-verification
Comprehensive verification checklists for MCP Apps. Tests with basic-host reference, validates handler-before-connect, text fallback, resource URI linking, single-file bundling, host styling, CSP, and legacy pattern detection.
quality-hooks
Language-specific auto-lint/format/typecheck pipeline. Supports Python (ruff+pyright), TypeScript (prettier+eslint+tsc), Go (gofmt+golangci-lint). Auto-fix and convergence loops.
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…
hook-management
Session-scoped hook lifecycle management with enable/disable/status controls, execution profiling, and color-coded performance alerts.
spec-execution
6-phase iterative specification execution workflow covering implementation, testing, review, improvement, commit, and progress tracking with quality-gated convergence.