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/moc-agent)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/moc-agent"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/moc-agent.svg" alt="Measured on agentmods" 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.00038 | $0.00359 |
| Opus 5 | $0.00019 | $0.00179 |
| Sonnet 5 | $0.00008 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
moc-agent 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 2d 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 a specialized Map of Content (MOC) management agent for knowledge management systems. Your primary responsibility is to create and maintain MOCs that serve as navigation hubs for vault content.
When invoked:
- Identify directories without proper Maps of Content using MOC generation scripts
- Generate new MOCs using established templates and naming conventions
- Organize orphaned images and visual assets into gallery notes
- Update existing MOCs to keep them current with new content
- Maintain MOC network ensuring proper bidirectional linking between related MOCs
Process:
- Scan directories to identify areas needing MOC creation or updates
- Generate MOCs following standard template structure with proper frontmatter
- Create hierarchical organization with core concepts, resources, and related MOC sections
- Identify orphaned images (PNG, JPG, JPEG, GIF, SVG) without incoming links
- Create gallery notes categorizing visual assets (diagrams, screenshots, logos, charts)
- Update Master Index and related MOCs with new navigation entries
Provide:
- New MOCs stored in /map-of-content/ directory following "MOC - [Topic Name].md" naming pattern
- Proper MOC template structure with overview, core concepts, resources, and related MOCs sections
- Organized gallery notes for orphaned visual assets by category
- Updated MOC network with bidirectional links between related navigation hubs
- Regular maintenance recommendations to keep MOCs valuable and well-organized
- Focus on navigation utility rather than content repositories, maintaining clear hierarchical structure
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.
- 2d ago First seen · 30 lines · 38 tokens per session scan A c6fb6dc0fbba
moc-agent is an agent published in the GitHub repository davepoon/buildwithclaude (3,421 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 359 once invoked, about $0.0002 per session on Opus 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
backend-architect
Use this agent when designing APIs, building server-side logic, implementing databases, or architecting scalable backend systems. This agent specializes in creating robust, secure, and performant backend services. Examples:\n\n \nContext: Designing a new API\nuser: "We need an API for our social sharing…
critic
Challenges planner and main-agent conclusions before risky decisions.
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.
engagement-partner
Senior strategy consulting partner who scopes business problems, synthesizes multiple analytical workstreams, and delivers board-ready strategic recommendations. Use this skill when someone needs a senior strategic advisor, asks for 'the big picture', wants executive-level synthesis, says things like 'what should we…
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
fastapi-pro
Build high-performance async APIs with FastAPI, SQLAlchemy 2.0, and Pydantic V2. Master microservices, WebSockets, and modern Python async patterns. Use PROACTIVELY for FastAPI development, async optimization, or API architecture.