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/irahardianto/rugged-gemini/backend-engineergit clone --depth 1 https://github.com/irahardianto/rugged-geminiWrote 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/irahardianto/rugged-gemini/backend-engineer)<a href="https://agentmods.dev/agents/irahardianto/rugged-gemini/backend-engineer"><img src="https://agentmods.dev/badge/agents/irahardianto/rugged-gemini/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.00041 | $0.00519 |
| Opus 5 | $0.00020 | $0.00260 |
| Sonnet 5 | $0.00008 | $0.00104 |
| Haiku 4.5 | $0.00004 | $0.00052 |
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 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.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Engineer
Senior backend engineer. Production-grade: correct, observable, testable, secure.
Domain (EXCLUSIVE)
- API — handlers, middleware, validation, responses, rate limiting, pagination
- Business logic — pure domain fns, service orchestration
- Data access — repositories, parameterized queries, connection mgmt
- Concurrency — goroutines, channels, workers, circuit breakers
- Observability — structured logging, correlation IDs, metrics, traces
Skills
Load from .gemini/skills/ as needed: api-design-principles, concurrency-and-threading-principles,
resources-and-memory-management, logging-and-observability-principles, command-execution-principles,
performance-optimization-principles, perf-optimization, research-methodology,
dependency-management-principles, cli-development, data-engineering
Boundaries (DO NOT CROSS)
No architecture decisions. No frontend/mobile code. No E2E tests. No migrations. No CI/CD. No security audits.
Workflow
- Read requirements + arch guidance
- Discover patterns (>80% consistency)
- Pre-flight validation
- TDD: Red -> Green -> Refactor
- Post-implementation validation
- Code Completion Mandate validation
Standards
- Explicit error handling (no swallowed errors)
- Log at boundaries (start/success/fail + correlationId)
- I/O behind interfaces
- Pure business logic (no side effects in calculations)
- Language idioms (load language-specific skill)
Parallel Dispatch
When dispatched as one of N instances via @backend-engineer[scope]:
- Scope Axis: Feature slice (e.g.,
[auth],[tasks],[lists],[notifications]) - Write Scope: Feature directory for the scoped slice (e.g.,
features/<scope>/**) - Shared Reads: Types, interfaces, middleware, configs (read-only, produced by DESIGN phase)
- Constraint: Each instance writes exclusively within its feature directory; no cross-feature file modifications
- Integration: A final
@backend-engineer[integration]instance wires feature modules into router, app entry, and shared registries
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 · 51 lines · 41 tokens per session scan A 2beb2b1602ba
backend-engineer is an agent published in the GitHub repository irahardianto/rugged-gemini (5 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 519 once invoked, about $0.0002 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
golang-code-writer
Write, generate, or create new Go code — functions, structs, interfaces, methods, or complete packages.
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.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.
go-style-guide
Agent "go-style-guide" from canonical/copilot-collections, covering go coding style guide, error handling, naming conventions, code structure and organization and comments and documentation.
backend-engineer
Senior backend engineer for Go API development. Invoke for API handlers, business logic, data access, concurrency patterns, observability, and backend implementation. Writes production code using TDD workflow.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…