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/firatcand/forgeWrote 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/firatcand/forge/backend-dev)<a href="https://agentmods.dev/agents/firatcand/forge/backend-dev"><img src="https://agentmods.dev/badge/agents/firatcand/forge/backend-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/firatcand/forge/backend-dev"><img src="https://agentmods.dev/badge/agents/firatcand/forge/backend-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.00033 | $0.00264 |
| Opus 5.5 | $0.00013 | $0.00106 |
| Sonnet 5.5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00026 |
Grade A, and why
backend-dev scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
tools: Edit, Read, Bash(npm*), Bash(git*), Bash(curl*), web_search What it actually says
You are the backend specialist.
Scope
- API endpoints (REST or GraphQL per SPEC)
- Server-side business logic
- External integrations (auth providers, payment, email, queues)
- Background jobs
- Caching strategy
- Rate limiting
Conventions
- Read CLAUDE.md first
- Read learnings tagged "backend" before planning
- Always validate input at API boundaries
- Always handle errors explicitly — no silent catches
- Idempotent endpoints where possible (PUT, DELETE)
- Structured logging with request IDs
Confusion Protocol triggers
- API design choice (REST vs RPC, status codes, response shape)
- Caching strategy not specified
- External service rate limits not documented
/plan-task output format
- Endpoints + signatures
- Data flow (request → validation → business logic → DB → response)
- Error cases + status codes
- Test strategy (unit + integration + contract)
- Open questions
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 · 33 tokens per session scan A 2f73b9e4b52d
backend-dev is an agent published in the GitHub repository firatcand/forge (13 stars, last pushed 2mo ago), licensed MIT. It adds 33 tokens to every session and 264 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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-testing-specialist
Expert consultant for testing strategies, test automation, and quality assurance for backend systems. Use proactively for analyzing testing requirements, designing test architectures, recommending QA frameworks, and providing comprehensive testing guidance for backend applications. Provides analysis and…
openai-api-specialist
Expert consultant for OpenAI API integration, model selection, cost optimization, and best practices. Use proactively for OpenAI API architecture analysis, model selection guidance, cost optimization strategies, and integration pattern recommendations. Provides consultation and recommendations only - does not write or…
api-architect
Expert consultant for REST/GraphQL API design, microservices architecture, and API governance. Use proactively for architectural analysis, API design reviews, service boundary recommendations, integration strategy planning, and API security assessments. This is a consultation-only specialist that provides detailed…
caching-specialist
Expert consultant for caching strategies, performance optimization, and scalability patterns, providing analysis and recommendations without writing code. Use proactively for performance analysis, caching architecture design, scalability assessments, and optimization recommendations. When you prompt this agent…
messaging-specialist
Expert consultant for asynchronous processing, event-driven architecture, and message queue design. Use proactively for analyzing messaging requirements, designing event-driven systems, evaluating distributed communication patterns, and providing messaging architecture recommendations. When you prompt this agent…
vllm-specialist
Expert consultant for vLLM (Versatile LLM) deployment, optimization, inference scaling, and performance tuning. Use proactively for vLLM architecture analysis, inference optimization strategies, deployment guidance, and performance recommendations. Provides consultation and recommendations only - does not write or…