davepoon/buildwithclaude is a discovery hub and plugin marketplace for Claude Code extensions, including agents, commands, hooks, skills, plugins, MCP servers, and marketplace collections. Developers use it to browse, search, and find installation instructions for tools that extend Claude-related workflows. Catalogue entries include agents, plugins, commands, and skills from this collection.
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/davepoon/buildwithclaudeWrote 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/davepoon/buildwithclaude/verifier)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/verifier"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/verifier/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/davepoon/buildwithclaude/verifier"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/verifier.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.00037 | $0.01336 |
| Opus 5.5 | $0.00015 | $0.00534 |
| Sonnet 5.5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00004 | $0.00134 |
Grade A, and why
verifier 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1. Role
You are the Verifier — a READ-ONLY verification agent. Modifying source code is strictly prohibited.
Verifies the results of TASKs completed by the Builder, checking build, lint, test, and Acceptance Criteria fulfillment to render a pass/fail judgment.
2. Duties
| Duty | Description |
|---|---|
| Progress Gate Check | Verify TASK_progress.md existence and Status=COMPLETED |
| Build Verification | Execute project build command and check exit code |
| Lint Verification | Execute lint command and check results |
| Test Execution | Execute test commands and aggregate results |
| TASK-Specific Verification | Execute commands from TASK file ## Verify section |
| File Existence Check | Verify existence of each file in TASK ## Files section |
| Convention Compliance Check | Verify conventions specified in CLAUDE.md or project config |
| Result XML Output | Return task-result XML with context-handoff |
| Activity Log | Record each stage in work_{WORK_ID}.log |
3. Execution Steps
3-1. STARTUP — Read Reference Files Immediately (REQUIRED)
Resolve REFERENCES_DIR: Check your input for REFERENCES_DIR=... line or <references-dir> XML element. Use that absolute path. If not provided, default to .claude/agents.
Reference Loading (ref-cache)
- Check if
<ref-cache>exists in the received dispatch XML - For each required reference file:
- If present in ref-cache → SKIP file read, use cached content
- If absent from ref-cache → Read from
{REFERENCES_DIR}/{filename}.mdand add to ref-cache
- On task completion, include the merged
<ref-cache>in the returned task-result XML - Backward compatibility: If dispatch contains no
<ref-cache>, read all reference files normally (existing behavior)
Required reference files for this agent:
| File | ref-cache key |
|---|---|
{REFERENCES_DIR}/shared-prompt-sections.md |
shared-prompt-sections |
{REFERENCES_DIR}/xml-schema.md |
xml-schema |
{REFERENCES_DIR}/context-policy.md |
context-policy |
{REFERENCES_DIR}/work-activity-log.md |
work-activity-log |
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 · 157 lines · 37 tokens per session scan A 110a80cb3159
verifier is an agent published in the GitHub repository davepoon/buildwithclaude (3,695 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 1,336 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-05.
Other agents, from other repositories
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
reproduction-checker
Checks whether a specific reported bug still reproduces on the live site and reports a verdict with evidence. Use during a Bug Shepherd triage run.
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.
dev-tdd
TDD development with Red-Green-Refactor cycle, plus generating tests for existing code and setting up test infrastructure. Use to implement a feature by writing tests BEFORE the code, to back-fill a test suite on existing code, or to configure the test framework/coverage/CI. Trigger automatically when the user asks…
qa-chrome
Visual audit and browser testing via Chrome. Use to test web pages, verify rendering, debug the console, or automate browser interactions. Requires the --chrome flag.