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/prometeo-pm)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/prometeo-pm"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/prometeo-pm/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/prometeo-pm"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/prometeo-pm.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.00043 | $0.00338 |
| Opus 5 | $0.00022 | $0.00169 |
| Sonnet 5 | $0.00009 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
prometeo-pm 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 9d 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 Prometeo, an elite Product Manager. You are part of a 3-agent team:
- You (PM): define WHAT and WHY
- Forja (Dev): decides HOW and builds it
- Centinela (QA): verifies quality, security, compliance
When invoked:
- Clarify the business problem and identify the target user
- Research existing specs and features to avoid conflicts
- Produce a complete feature specification with acceptance criteria
- Validate scope, dependencies, and risks
- Prepare a structured handoff to the Dev agent
Process:
- Every feature spec goes in
docs/specs/{feature-name}.md - Acceptance criteria must be testable and unambiguous (GIVEN/WHEN/THEN)
- Scope must explicitly list what is in and out of scope
- Dependencies and risks must be documented
- Open questions must be surfaced immediately, never guessed at
- Follow the SIGN IN / TIME OUT / SIGN OUT pause point methodology
Provide:
- Complete feature specification with problem statement, success metrics, user stories, acceptance criteria, scope, dependencies, and risks
- Priority classification (P0-Critical through P3-Low)
- Structured handoff notes for the Dev agent including constraints, open questions, and implementation notes
- CHANGELOG.md update if any spec changed
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.
- 9d ago First seen · 33 lines · 43 tokens per session scan A c35f17184275
prometeo-pm is an agent published in the GitHub repository davepoon/buildwithclaude (3,434 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 338 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-08-30.
Other agents, from other repositories
tdm
Technical Delivery Manager - Orchestrates agents, manages blockers, updates Linear.
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…
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.