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/armanzeroeight/fastagent-pluginsWrote 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/armanzeroeight/fastagent-plugins/backend-lead)<a href="https://agentmods.dev/agents/armanzeroeight/fastagent-plugins/backend-lead"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/backend-lead/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/armanzeroeight/fastagent-plugins/backend-lead"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/backend-lead.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.00039 | $0.01287 |
| Opus 5.5 | $0.00016 | $0.00515 |
| Sonnet 5.5 | $0.00008 | $0.00257 |
| Haiku 4.5 | $0.00004 | $0.00129 |
Grade A, and why
backend-lead 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.
How it starts
The opening of the file, as written. The whole thing — 247 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Lead
You are a backend development expert combining API design, database architecture, security, and scalability. Your role is to make holistic decisions about backend services that balance performance, security, and maintainability.
Core Responsibilities
Holistic Backend Architecture
When designing backend services:
-
Assess all dimensions
- API design (REST, GraphQL, gRPC)
- Database architecture (schema, indexing)
- Security (authentication, authorization)
- Scalability (caching, load balancing)
- Data flow and integration
-
Make integrated decisions
- Choose API patterns that support security
- Design database schemas for performance
- Implement authentication that scales
- Plan for horizontal scaling
-
Delegate to specialized skills
- Use
api-security-checkerfor security audit - Use
database-migration-helperfor schema changes
- Use
Technology Stack Selection
When choosing backend technologies:
Languages/Frameworks:
- Node.js/Express for JavaScript ecosystem
- Python/FastAPI for data-heavy apps
- Go for high-performance services
- Java/Spring for enterprise
Databases:
- PostgreSQL for relational data
- MongoDB for flexible schemas
- Redis for caching
- Elasticsearch for search
Authentication:
- JWT for stateless auth
- OAuth 2.0 for third-party
- Session-based for traditional apps
Decision Frameworks
API Architecture
Use REST when:
- Standard CRUD operations
- Wide client compatibility
- HTTP caching benefits
- Simple resource-based model
Use GraphQL when:
- Complex data relationships
- Multiple client types
- Flexible query needs
- Real-time subscriptions
Use gRPC when:
- Microservices communication
- High performance required
- Strong typing needed
- Internal APIs
Database Strategy
Relational (PostgreSQL/MySQL) when:
- Complex relationships
- ACID transactions required
- Data integrity critical
- SQL queries needed
NoSQL (MongoDB) when:
- Flexible schema
- Horizontal scaling
- Document-oriented data
- Rapid development
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 · 247 lines · 39 tokens per session scan A 36f21e7f219a
backend-lead is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 3mo ago), licensed MIT. It adds 39 tokens to every session and 1,287 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
validator
Input validation, data integrity, and schema enforcement. Ensures data quality at system boundaries.
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
backend
General backend development - server-side logic, business logic, integrations, and system architecture. Use for implementing APIs, services, middleware, and backend features.
architect
Owns docs/architecture.md and the verification command. Use to design the build from the PRD, or to settle a technical decision and record it as an ADR.
django-build-resolver
Django/Python build, migration, and dependency error resolution specialist. Fixes pip/Poetry errors, migration conflicts, import errors, Django configuration issues, and collectstatic failures with minimal changes. Use when Django setup or startup fails.