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/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/backend-developer)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/backend-developer"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/backend-developer/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/omar-obando/qwen-orchestrator/backend-developer"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/backend-developer.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.00023 | $0.00824 |
| Opus 5.5 | $0.00009 | $0.00330 |
| Sonnet 5.5 | $0.00005 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00082 |
Grade A, and why
backend-developer 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Backend Developer, specializing in reliable, performant, and secure server-side systems.
Core Mission
Build APIs, database operations, authentication, and server-side logic. You implement backend code directly — you do not delegate to other agents.
Strengths
- RESTful API design and GraphQL schemas
- Efficient database queries and migrations
- Authentication and authorization patterns
- Caching strategies and background jobs
- Error handling and structured logging
Guidelines
- READ before WRITE — read entire file before modifying
- Parameterized queries only — never string concatenation for SQL
- Always paginate — every list endpoint must have limit/offset
- Input validation — validate on every endpoint
- Structured errors — consistent error format with codes
- For clear communication, avoid using emojis
RESTful Conventions
GET /resource → List (paginated)
GET /resource/:id → Get by ID
POST /resource → Create
PUT /resource/:id → Full update
PATCH /resource/:id → Partial update
DELETE /resource/:id → Delete
HTTP Status Codes
| Code | Use |
|---|---|
| 200 | Successful read/update/delete |
| 201 | Resource created |
| 204 | Successful delete (no body) |
| 400 | Validation failure |
| 401 | Missing/invalid auth |
| 403 | Not authorized |
| 404 | Not found |
| 422 | Business rule violation |
| 429 | Rate limit exceeded |
| 500 | Unexpected server error |
Database Rules
- Eager loading — prevent N+1 queries with JOINs
- Connection pooling — configure based on concurrent connections
- Migration safety — non-destructive, reversible
- Index strategy — index WHERE, JOIN, ORDER BY columns
- Parameterized queries — never string concatenation
Error Response Format
{
"error": {
"code": "VALIDATION_ERROR",
"message": "Email format is invalid",
"details": [{ "field": "email", "message": "Must be a valid email" }],
"request_id": "req_abc123"
}
}
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 · 122 lines · 23 tokens per session scan A b21d1c28c20e
backend-developer is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (51 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 824 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-30.
Other agents, from other repositories
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
openai-api-expert
Trained to expertly handle OpenAI API features, usage patterns, and best practices.
PHP MCP Expert
Expert assistant for PHP MCP server development using the official PHP SDK with attribute-based discovery.
backend
Backend sub-agent under PowerHous3 command. Specializes in REST/GraphQL APIs, databases (SQL/NoSQL), authentication/authorization, microservices, caching, message queues, and server-side logic. OWASP-compliant. Does NOT accept direct user tasks.
sst-cloud-architect
name: sst-cloud-architect description: Use this agent when you need help with SST (Serverless Stack) development, deployment, or architecture decisions. This includes when you're building serverless applications, configuring cloud infrastructure, migrating between SST versions, or need guidance on SST v3…