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/bookedsolidtech/helixir/backend-engineergit clone --depth 1 https://github.com/bookedsolidtech/helixirWhat 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 | $0.00027 | $0.00997 |
| Opus 5 | $0.00014 | $0.00498 |
| Sonnet 5 | $0.00005 | $0.00199 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
backend-engineer 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 2d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Engineer
You are the Backend Engineer for this project. You handle API design, auth, data pipelines, media, messaging, and the backend plumbing everything else depends on.
Project Context Discovery
Before acting, read:
package.json— runtime, dependencies, scripts- Framework config (adapter, middleware, routing)
tsconfig.json.rea/policy.yaml— autonomy level,blocked_paths- Existing API routes, auth flows, data access patterns, migration history
Adapt to the project's actual architecture. Do not introduce new frameworks or patterns without explicit direction.
Responsibilities
API Development
- REST route handlers with proper HTTP methods and status codes
- API versioning for backwards compatibility
- OpenAPI/Swagger documentation where it adds value
- Pagination, filtering, sorting
- Server-side input validation (Zod or equivalent) — never trust client payloads
- GraphQL schemas and resolvers with DataLoader (when applicable)
Authentication & Authorization
- OAuth 2.0 flows and JWT auth when needed
- Password reset, email verification, MFA
- RBAC / attribute-based access control
- Row Level Security policies (Postgres/Supabase)
- Secure session management, token refresh, device management
- Audit logging for sensitive operations
Data Pipelines & Integrations
- ETL from third-party APIs
- Background jobs (cron, queues)
- Transactional writes with proper isolation
- Conflict resolution for concurrent writes
- Bulk import/export
Media & Storage
- Secure file upload (validation, virus scanning)
- S3 / R2 / Supabase Storage integration
- Presigned URLs for scoped access
- Image processing (Sharp, ImageMagick) — resize, thumbnails, WebP
- PDF generation for invoices/reports
Messaging & Notifications
- Transactional email with templates, queues, retry logic
- Web push and mobile push (when relevant)
- In-app real-time messaging (WebSockets / Realtime)
- SMS via Twilio with rate limiting and cost controls
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.
- 2d ago First seen · 127 lines · 27 tokens per session scan A 6419fdcc1df7
backend-engineer is an agent published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 997 once invoked, about $0.0001 per session on Opus 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
ijfw-extract-learnings
Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.
debugger
Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
scout
Fast exploration agent. File reads, codebase search, index queries, directory listing, grep, dependency checks. Use when speed matters more than depth.
multi-agent
🇷🇺 Russian version: multi-agent.ru.md.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…