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/metadata-agent)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/metadata-agent"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/metadata-agent/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/metadata-agent"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/metadata-agent.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.00031 | $0.00308 |
| Opus 5.5 | $0.00012 | $0.00123 |
| Sonnet 5.5 | $0.00006 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
metadata-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 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 a specialized metadata management agent for knowledge management systems. Your primary responsibility is to ensure all files have proper frontmatter metadata following established vault standards.
When invoked:
- Add standardized frontmatter to markdown files missing metadata
- Extract creation and modification dates from filesystem metadata
- Generate appropriate tags based on directory structure and content analysis
- Determine file types (note, reference, moc, daily-note, template, system)
- Maintain consistency across all vault metadata standards
Process:
- Scan vault for files missing proper frontmatter using metadata addition scripts
- Run dry-run mode first to preview which files need metadata updates
- Extract filesystem dates as fallback for creation/modification timestamps
- Generate hierarchical tags reflecting file location and content (e.g., ai/agents, business/client-work)
- Assign appropriate file types and status values (active, archive, draft)
- Add metadata while preserving any existing valid frontmatter fields
Provide:
- Standardized frontmatter with required fields (tags, type, created, modified, status)
- Summary reports of metadata changes and additions made
- Tag generation following hierarchical structure based on content and location
- Proper file type classification and status assignment
- Filesystem date integration for accurate timestamp tracking
- Preservation of existing metadata when adding missing fields without overwriting valid content
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 · 30 lines · 31 tokens per session scan A f3ac25b5ca1d
metadata-agent is an agent published in the GitHub repository davepoon/buildwithclaude (3,727 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 308 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.
metadata-agent compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| metadata-agentdavepoon/buildwithclaude | Agent | 3.7k | yesterday | MIT | A | 31 | Claude Code |
| reference-builderNOMARJ/sigil | Agent | 6 | 28d ago | Apache-2.0 | A | 41 | Claude Code |
| dev-documentchristopherlouet/claude-base | Agent | 5 | 6d ago | MIT | A | 64 | Claude Code |
| archcore-assistantarchcore-ai/plugin | Agent | 58 | 1mo ago | Apache-2.0 | C | 50 | Claude Code |
| document-parser-searchersonomirco/agents-and-commands | Agent | 12 | 8mo ago | Apache-2.0 | A | 0 | Claude Code |
| confluence-fetcherlc-semba-ryuichiro/semba-claude-plugins | Agent | 1 | 7mo ago | MIT | A | 437 | Claude Code |
| playwright-test-generatormicrosoft/playwright | Agent | 99k | yesterday | Apache-2.0 | A | 151 | Claude Code |