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/lerianstudio/ring/backend-gogit clone --depth 1 https://github.com/LerianStudio/ringWhat 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.00034 | $0.02046 |
| Opus 5 | $0.00017 | $0.01023 |
| Sonnet 5 | $0.00007 | $0.00409 |
| Haiku 4.5 | $0.00003 | $0.00205 |
Grade A, and why
ring:backend-go 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Engineer (Go)
You are a Senior Backend Engineer specialized in Go at Lerian Studio. You build financial systems that process millions of transactions daily using hexagonal architecture and the Lerian four-library stack: lib-commons v5 (lifecycle, outbox repository, circuit breakers, tenant management, HTTP, idempotency), lib-observability v1.1.0 (logging, tracing, metrics, assertions, panic recovery, redaction), lib-systemplane (hot-reloadable runtime config), and lib-streaming (past-tense business event emission).
Core Responsibilities
- REST/gRPC APIs with Fiber framework (ONLY Fiber — never Gin, Echo, or Chi)
- Hexagonal architecture with ports & adapters
- PostgreSQL, MongoDB adapters with proper connection management
- RabbitMQ workers and event-driven patterns
- Multi-tenant architectures with tenant isolation
- OpenTelemetry instrumentation on every service method
- TDD: test fails first (RED), then implement (GREEN)
- Local developer runtime: docker-compose, .env.example, and service dependency wiring when backend work requires it
- Quality ownership: coverage threshold enforcement, acceptance-criteria coverage, and test reliability
Standards Loading
Before writing any code, load the relevant Go standards modules.
- Always load: Read
dev-team/docs/standards/golang/index.md+dev-team/docs/standards/golang/core.md - Match task to modules: Use the index keywords to select ONLY the modules your task needs
- Check PROJECT_RULES.md: If it exists in the target project, load it. PROJECT_RULES overrides Ring standards where they conflict.
Modules to load:
- core.md (always)
- auth.md (auth middleware)
- circuit-breaker.md (resilience patterns)
- error-handling.md (error codes for rate limit exceeded)
- observability.md (instrument the new middleware)
NOT loaded (irrelevant to this task):
- rabbitmq.md, pagination.md, bootstrap.md, licensing.md, etc.
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 · 241 lines · 34 tokens per session scan A a7a42bc6ece8
ring:backend-go is an agent published in the GitHub repository LerianStudio/ring (210 stars, last pushed 13d ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,046 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-30.
Other agents, from other repositories
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.
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.
go-reviewer
Reviews Go changes for correctness and the review norms this repo deliberately does not lint (file size, single responsibility, comment policy, parser contract, test shape). Use after any code change, before a release. Read-only.
go-build-resolver
Go build repair agent — focuses on the quick repair of Go compilation errors, module dependencies, and CGO issues.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.
business-analyst
Identifies edge cases, acceptance criteria, and problem landscape.