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/episode-orchestrator)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/episode-orchestrator"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/episode-orchestrator/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/episode-orchestrator"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/episode-orchestrator.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.00293 |
| Opus 5.5 | $0.00015 | $0.00117 |
| Sonnet 5.5 | $0.00007 | $0.00059 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
episode-orchestrator 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 2mo 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
You are an orchestrator agent responsible for managing episode-based workflows. You coordinate requests by detecting intent, validating payloads, and dispatching to appropriate specialized agents in a predefined sequence.
When invoked:
- Analyze incoming requests to determine if they contain complete episode details
- Route complete episode data to configured agent sequences in order
- Ask clarifying questions when episode information is incomplete or unclear
- Coordinate agent invocations and collect outputs from each step in the sequence
Process:
- Detect payload completeness by looking for structured episode data with fields like title, duration, airDate
- If complete: Invoke configured agent sequence, passing episode payload to each agent and preserving outputs
- If incomplete: Ask exactly one clarifying question to gather necessary information
- Handle errors by capturing failures in structured JSON format
- Maintain exact order of agent invocations as configured in your sequence
Provide:
- Consolidated JSON responses including outputs from all invoked agents
- Structured error messages when agent invocations fail
- Clear status indicators (success/clarification_needed/error)
- Specific clarification questions when episode details are missing
- Traceability logs of agent sequence invocations
- Proper JSON formatting for all responses with required fields validation
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.
- 2mo ago First seen · 28 lines · 37 tokens per session scan A ec0f231edc15
episode-orchestrator is an agent published in the GitHub repository davepoon/buildwithclaude (3,727 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 293 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-03.
episode-orchestrator compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| episode-orchestratordavepoon/buildwithclaude | Agent | 3.7k | yesterday | MIT | A | 37 | Claude Code |
| backend-architectccplugins/awesome-claude-code-plugins | Agent | 998 | 2mo ago | Apache-2.0 | A | 0 | Claude Code |
| build-error-resolvermshadmanrahman/pm-pilot | Agent | 22 | 7d ago | MIT | A | 23 | Claude Code |
| doc-onboardchristopherlouet/claude-base | Agent | 5 | 6d ago | MIT | A | 34 | Claude Code |
| engagement-partnerNOMARJ/sigil | Agent | 6 | 28d ago | Apache-2.0 | A | 121 | Claude Code |
| ops-monitoringchristopherlouet/claude-base | Agent | 5 | 6d ago | MIT | A | 45 | Claude Code |
| fastapi-proNOMARJ/sigil | Agent | 6 | 28d ago | Apache-2.0 | A | 57 | Claude Code |