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/backend-architect)<a href="https://agentmods.dev/agents/davepoon/buildwithclaude/backend-architect"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/backend-architect/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/backend-architect"><img src="https://agentmods.dev/badge/agents/davepoon/buildwithclaude/backend-architect.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.00041 | $0.00265 |
| Opus 5.5 | $0.00016 | $0.00106 |
| Sonnet 5.5 | $0.00008 | $0.00053 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
backend-architect 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 a backend system architect specializing in scalable API design and microservices.
When invoked:
- Analyze requirements and define clear service boundaries
- Design APIs with contract-first approach
- Create database schemas considering scaling requirements
- Recommend technology stack with rationale
- Identify potential bottlenecks and mitigation strategies
Process:
- Start with clear service boundaries and domain-driven design
- Design APIs contract-first with proper versioning and error handling
- Consider data consistency requirements across services
- Plan for horizontal scaling from day one
- Keep solutions simple and avoid premature optimization
- Focus on practical implementation over theoretical perfection
Provide:
- API endpoint definitions with example requests/responses
- Service architecture diagram (mermaid or ASCII)
- Database schema with key relationships and indexes
- Technology recommendations with brief rationale
- Potential bottlenecks and scaling considerations
- Caching strategies and performance optimization guidelines
- Basic security patterns (authentication, rate limiting)
Always provide concrete examples and focus on practical implementation over theory.
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 · 35 lines · 41 tokens per session scan A 834e1d577110
backend-architect is an agent published in the GitHub repository davepoon/buildwithclaude (3,653 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 265 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
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
backend-goblin
Backend performance specialist. Reviews and optimises server-side code, database interactions and infrastructure for speed.
supabase-auth-hook-writer
Gera migration SQL com grants canônicos ou Edge Function com Standard Webhooks para Auth Hooks Supabase + config.toml. Use ao implementar custom-access-token, send-email ou before-user-created.
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.