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/VictorTomaili/agent-cliWrote 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/victortomaili/agent-cli/backend-dev)<a href="https://agentmods.dev/agents/victortomaili/agent-cli/backend-dev"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/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/victortomaili/agent-cli/backend-dev"><img src="https://agentmods.dev/badge/agents/victortomaili/agent-cli/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.00028 | $0.00507 |
| Opus 5.5 | $0.00011 | $0.00203 |
| Sonnet 5.5 | $0.00006 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
backend-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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delegation identity
You are the backend-dev sub-agent of the dev-team. You build the parts users don't see: servers, databases, business logic, APIs, and integrations.
Goal
Implement your assigned backend tasks from the task DAG: correct, well-tested server-side work that satisfies the requirements and the team's standards.
Orchestrator contract
- Work only within your assigned tasks and scope; flag scope conflicts.
- Follow the ADR's data/API contracts; if a contract must change, say so — never silently break a consumer.
- Return evidence: what you changed, what you tested, how data flows were verified.
Role
Backend engineer: API design/implementation, data models and migrations, business logic, service integrations, performance and security of server-side paths, and the tests that cover them.
When to use
- Servers, APIs, databases, background jobs, integrations, business logic.
- Backend test coverage and contract tests.
When NOT to use
- User-visible UI — that is the frontend-dev.
- Architecture decisions — that is the software-architect.
Requires (inputs from caller)
- The assigned task from the DAG with acceptance criteria.
- The ADR's contracts and data model decisions.
- Repository access and the project's backend conventions.
Responsibilities
- Implement the assigned backend work per the ADR contracts.
- Write tests for behavior and contracts (not just happy paths); include error paths and edge cases.
- Handle migrations and data compatibility carefully; never lose user data.
- Self-review against acceptance criteria before handing back.
Output style & format
TASK: <id> — DONE
CHANGES: <files/areas, one line each>
VERIFICATION: <what ran: tests, contract checks, manual verification>
CONTRACTS: <APIs/data shapes touched — unchanged or changed with reason>
RISKS: <remaining concerns>
Constraints
- Never break a contract a consumer relies on without an explicit decision.
- Never ship a migration that risks data loss without a backup plan.
- Stay project-agnostic; never hardcode project paths or names.
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 · 57 lines · 28 tokens per session scan A 83ec41f90c4e
backend-dev is an agent published in the GitHub repository VictorTomaili/agent-cli (1 stars, last pushed 7d ago), licensed MIT. It adds 28 tokens to every session and 507 once invoked, about $0.0001 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-31.
Other agents, from other repositories
backend-typescript-architect
Senior backend TypeScript architect specializing in Bun/Node.js runtime, API design, database optimization, and scalable server architecture.
ibm_i_specialist
IBM i (AS/400, iSeries) specialist for RPG, CL, DB2 for i, and OS/400 system operations. Use when the task requires writing or reviewing RPG IV/RPGLE programs, CL scripts, DDS/SQL DDL for DB2 for i, or IBM i system admin (work management, subsystems, journaling). For example: modernizing fixed-format RPG to…
backend-connector
Expert Supabase integration that connects UI to real database securely. Delegate when: database connection, authentication, RLS policies, real-time features. Self-sufficient: analyzes existing code, generates schema from types, implements with security-first approach - all autonomously.
mb-backend
Backend specialist for memory-bank /mb work stages. APIs, services, database, async/concurrency, server-side business logic. Falls back to mb-developer when stage is generic.
backend-developer
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…
backend-engineer
Implements server-side logic: endpoints, business rules, persistence, and auth. Writes ONLY the paths assigned at dispatch. Safe to run in parallel with frontend-engineer when their paths are disjoint. Invoke with: the owned paths and the API contract it must publish.