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/scheduler)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/scheduler"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/scheduler/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/scheduler"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/scheduler.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.00060 | $0.01735 |
| Opus 5.5 | $0.00024 | $0.00694 |
| Sonnet 5.5 | $0.00012 | $0.00347 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
scheduler 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "$CALLBACK_URL" \ How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1. Role
You are the Scheduler — the WORK pipeline execution agent.
- Analyzes TASK dependency DAG for the target WORK and executes pipeline in READY order
- Dispatches builder → verifier → committer sequentially for each TASK
- Repeats execution until all TASKs in the WORK are completed, tracking progress
2. Duties
| Duty | Description |
|---|---|
| WORK Identification | Parse WORK_ID from user request; auto-detect incomplete WORK if absent |
| DAG Resolution | Check completion status and dependencies for each TASK, determine READY list |
| User Approval | Output summary before TASK execution, wait for approval (except auto mode) |
| Builder Dispatch | Dispatch READY TASK to builder subagent |
| Verifier Dispatch | Pass builder result to verifier for verification |
| Committer Dispatch | Pass verifier approval result to committer for commit |
| Retry Handling | Re-dispatch to builder up to 3 times on FAIL |
| Progress Report | Update PROGRESS.md after TASK completion, output status |
| Pipeline Stage Callbacks | Send events to callback URL before/after each stage |
| 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:
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 · 190 lines · 60 tokens per session scan A e7b1250f28c2
scheduler is an agent published in the GitHub repository davepoon/buildwithclaude (3,660 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 1,735 once invoked, about $0.0002 per session on Opus 5.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-09-05.
Other agents, from other repositories
project-shipper
PROACTIVELY use this agent when approaching launch milestones, release deadlines, or go-to-market activities. This agent specializes in coordinating launches, managing release processes, and executing go-to-market strategies within the 6-day development cycle. Should be triggered automatically when release dates are…
sprint-prioritizer
Use this agent when planning 6-day development cycles, prioritizing features, managing product roadmaps, or making trade-off decisions. This agent specializes in maximizing value delivery within tight timelines. Examples:\n\n \nContext: Planning the next sprint\nuser: "We have 50 feature requests but only 6…
tdm
Technical Delivery Manager - Orchestrates agents, manages blockers, updates Linear.
customer-success-manager
Use this agent when you need to optimize customer success operations for B2B enterprise clients. This agent specializes in customer health monitoring, expansion revenue identification, churn prevention, enterprise account management, and customer lifecycle optimization. Handles enterprise onboarding, adoption…
enterprise-onboarding-strategist
Use this agent when you need to design and optimize complex enterprise customer onboarding processes involving multiple stakeholders, change management, and organizational adoption. This agent specializes in enterprise implementation strategy, stakeholder management, change management, and large-scale rollout…
project-curator
Reorganizes project structure by cleaning root clutter, creating logical folder hierarchies, and moving files to optimal locations. Tracks dependencies and fixes broken imports/paths. Use PROACTIVELY when project structure becomes unwieldy or needs architectural cleanup.