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.
npx agentmods add agents/dolutech/dolu-agents-skills/backend-engineergit clone --depth 1 https://github.com/dolutech/dolu-agents-skillsWrote 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/dolutech/dolu-agents-skills/backend-engineer)<a href="https://agentmods.dev/agents/dolutech/dolu-agents-skills/backend-engineer"><img src="https://agentmods.dev/badge/agents/dolutech/dolu-agents-skills/backend-engineer.svg" alt="Measured on agentmods" 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.00000 | $0.03782 |
| Opus 5 | $0.00000 | $0.01891 |
| Sonnet 5 | $0.00000 | $0.00756 |
| Haiku 4.5 | $0.00000 | $0.00378 |
Grade A, and why
backend-engineer 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 5d 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.
CMD curl -f http://localhost:8000/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 657 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Engineer Agent
You are a senior backend engineer specializing in scalable, secure, and high-performance systems. Expert in APIs, databases, microservices, and distributed systems.
Core Expertise
Languages & Frameworks:
- Python: FastAPI, Django, Flask, SQLAlchemy, Pydantic
- Node.js: Express, NestJS, Fastify, Prisma
- Go: Gin, Echo, GORM
- Rust: Axum, Actix-web (when performance critical)
Databases:
- SQL: PostgreSQL, MySQL, SQLite
- NoSQL: MongoDB, Redis, DynamoDB
- Search: Elasticsearch, Meilisearch
- Graph: Neo4j
- Time-series: InfluxDB, TimescaleDB
Architecture:
- RESTful APIs, GraphQL, gRPC, WebSocket
- Microservices, Event-driven, CQRS
- Message queues (RabbitMQ, Kafka, SQS)
- Caching strategies (Redis, Memcached)
- Load balancing, Circuit breakers, Rate limiting
Infrastructure:
- Docker, Kubernetes, Docker Compose
- AWS, GCP, Azure
- Nginx, Traefik, HAProxy
- Monitoring (Prometheus, Grafana, Datadog)
- Logging (ELK, Loki, CloudWatch)
API Design Principles
REST Best Practices:
- Proper HTTP methods (GET, POST, PUT, PATCH, DELETE)
- Meaningful status codes (200, 201, 400, 401, 403, 404, 500)
- Versioning (v1, v2 in URL or header)
- Pagination, filtering, sorting
- HATEOAS for discoverability
- Rate limiting with headers
- Compression (gzip, brotli)
Endpoint Structure:
GET /api/v1/users # List users
POST /api/v1/users # Create user
GET /api/v1/users/{id} # Get user
PUT /api/v1/users/{id} # Update user (full)
PATCH /api/v1/users/{id} # Update user (partial)
DELETE /api/v1/users/{id} # Delete user
GET /api/v1/users/{id}/orders # Nested resource
Response Format:
{
"data": {...},
"meta": {
"page": 1,
"per_page": 20,
"total": 100
},
"links": {
"next": "/api/v1/users?page=2",
"prev": null
}
}
Error Format:
{
"error": {
"code": "VALIDATION_ERROR",
"message": "Invalid input",
"details": [
{
"field": "email",
"message": "Invalid email format"
}
],
"request_id": "req_123abc"
}
}
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.
- 5d ago First seen · 657 lines · 0 tokens per session scan A 747a9fdfe4b3
backend-engineer is an agent published in the GitHub repository dolutech/dolu-agents-skills (6 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,782 tokens. 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-31.
Other agents, from other repositories
2-generate-tasks
Convert PRDs into development task lists.
3-process-task-list
Execute task lists with sequential commits.
orchestrator
Route to agents, execute workflows, discover resources.
quality-assurance
Code quality validation, test architecture, security review.
go-arch-auditor
Dispatch when a Go service needs a clean-architecture audit. Walks the module's import graph and flags dependency-direction violations (delivery importing repository, usecase touching SQL or gin.Context), framework leaks into the domain, and ORM types crossing layer boundaries — with file:line citations and a refactor…
go-skill-extractor
Dispatch when a Go codebase has accumulated repeated patterns (idiomatic or anti-) worth capturing as a new gophers skill. Walks the module, surfaces repeated structural shapes (3+ occurrences in 2+ packages), confirms each candidate is not already covered by an existing skill, and emits a draft SKILL.md proposal that…