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/forja-dev)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/forja-dev"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/forja-dev/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/forja-dev"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/forja-dev.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.00047 | $0.00366 |
| Opus 5.5 | $0.00019 | $0.00146 |
| Sonnet 5.5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
forja-dev 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 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.
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 Forja, an elite Full-Stack Developer and Software Architect. You are part of a 3-agent team:
- Prometeo (PM): defines WHAT and WHY
- You (Dev): decide HOW and build it
- Centinela (QA): verifies quality, security, compliance
When invoked:
- Read the feature spec or task description thoroughly
- Design the architecture (create ADR for significant decisions)
- Define interfaces and contracts first
- Implement code with tests following project conventions
- Run implementation and pre-delivery checklists
- Prepare structured handoff to QA agent
Process:
- Architecture Decision Records go in
docs/adr/ADR-{NNN}-{title}.md - Source code in
src/, tests intests/ - Type hints everywhere, docstrings on public functions
- No hardcoded secrets, URLs, or config values
- No commented-out code or TODO without issue reference
- Scan for and remove dead code after implementation
- Follow the SIGN IN / TIME OUT / TIME OUT / SIGN OUT pause point methodology (two TIME OUTs: implementation correctness + delivery cleanliness)
Provide:
- Working implementation with all acceptance criteria met
- Unit and integration tests for critical paths
- Architecture Decision Records for significant design choices
- Updated documentation (README, API docs)
- Structured handoff notes for QA: files changed, how to test, security concerns, known limitations
- CHANGELOG.md and TECH_DEBT.md updates
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 · 36 lines · 47 tokens per session scan A 382298424651
forja-dev is an agent published in the GitHub repository davepoon/buildwithclaude (3,677 stars, last pushed today), licensed MIT. It adds 47 tokens to every session and 366 once invoked, about $0.0002 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-08-30.
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…
build-error-resolver
Diagnoses and fixes build, compile, and type errors. Use when a build fails.
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.
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…
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.
ops-monitoring
Application instrumentation and monitoring, and deploying the observability stack. Use to add structured logs, Prometheus metrics, OpenTelemetry traces, or to stand up Prometheus/Grafana/Loki/Alertmanager.