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/committer)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/committer"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/committer/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/committer"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/committer.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.00036 | $0.01958 |
| Opus 5.5 | $0.00014 | $0.00783 |
| Sonnet 5.5 | $0.00007 | $0.00392 |
| Haiku 4.5 | $0.00004 | $0.00196 |
Grade A, and why
committer 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1. Role
You are the Committer — the agent that generates the result report for a verified TASK and then performs git commit.
- Gate check on builder's progress.md, then generate result.md
- Update PROGRESS.md → WORK-LIST check → git commit → send TaskCallback
2. Duties
| Duty | Description |
|---|---|
| Gate Check | Verify progress.md existence and Status: COMPLETED |
| Result Report Generation | Create works/{WORK_ID}/TASK-XX_result.md (includes builder/verifier context-handoff) |
| PROGRESS.md Update | Current TASK → ✅ Done, add timestamp, check unblocked TASKs |
| Git Commit | Explicit staging of works/{WORK_ID}/ and builder-changed files, then git commit — execute after confirming result file exists |
| TaskCallback Transmission | Send completion notification to TaskCallback URL in CLAUDE.md |
| Result Report | Report to scheduler in XML task-result format |
| 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}/file-content-schema.md |
file-content-schema |
{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 · 210 lines · 36 tokens per session scan A fd7bf8c5c4de
committer is an agent published in the GitHub repository davepoon/buildwithclaude (3,653 stars, last pushed yesterday), licensed MIT. It adds 36 tokens to every session and 1,958 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
ops-cost
Cost tracking and optimization — Claude Code token consumption (metrics, trends) and cloud infrastructure FinOps (right-sizing, commitments, savings).
module-registrar
Register new modules in the Datacore ecosystem. Use this agent: When creating a new module for community contribution For :AI:module:register: tagged tasks To update CATALOG.md with new module entries To create GitHub repos and PRs for module registration Part of the community contribution workflow (DIP-0001).
gsd-executor
Executes GSD plans with atomic commits, deviation handling, checkpoint protocols, and state management. Spawned by execute-phase orchestrator or execute-plan command.
repo-doctor
Collection health triage agent. Use when the user wants to know what needs attention across their repository collection. Runs a fixed multi-query workflow and produces a prioritized action list. Triggers on: "check my repos", "what needs attention", "collection health", "repo audit", "which repos need work", "repo…
queue-rebalancer
Dependency-aware unblock lane coordinator. USE FOR: reordering open PRs/issues by dependency to unblock broken builds fast, cherry-picking blocker fixes from issue and PR queues into a focused unblock group, and returning work to normal queue order after verification. DO NOT USE FOR: sprint capacity planning…
Demonstrate
Agent for demonstrating VS Code features.