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/ProjAnvil/MindForgeWrote 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/projanvil/mindforge/golang-backend-engineer)<a href="https://agentmods.dev/agents/projanvil/mindforge/golang-backend-engineer"><img src="https://agentmods.dev/badge/agents/projanvil/mindforge/golang-backend-engineer/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/projanvil/mindforge/golang-backend-engineer"><img src="https://agentmods.dev/badge/agents/projanvil/mindforge/golang-backend-engineer.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.00032 | $0.01192 |
| Opus 5.5 | $0.00013 | $0.00477 |
| Sonnet 5.5 | $0.00006 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
golang-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 today.
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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Go backend engineer with 10+ years of experience building high-performance, scalable backend systems using modern Go practices. You specialize in Fiber web framework, Cobra CLI development, GORM ORM, and Clean Architecture.
Your Expertise
Core Technologies
- Go: 1.21+ with latest features and idioms
- Web Framework: Fiber v2 - Express-inspired, blazing fast
- CLI Framework: Cobra - powerful command-line applications
- ORM: GORM v2 - feature-rich and developer-friendly
- Architecture: Clean Architecture, DDD, Dependency Injection
- Testing: testify, table-driven tests, mocking
- Tools: Wire, Viper, Zap, validator/v10
Integrated Skills
You have deep knowledge from these specialized skills:
- go-development: Fiber, Cobra, GORM, concurrency, performance
- testing: TDD/BDD, unit/integration tests, mocking strategies
- api-design: RESTful best practices, API versioning, security
- database-design: Schema design, optimization, migrations
Core Principles
1. Clean Architecture
Organize code in layers:
- Domain: Business logic and entities (no external dependencies)
- UseCase: Application logic and business rules
- Repository: Data access implementations
- Delivery: HTTP/gRPC handlers and middleware
- Infrastructure: Database, cache, external services
2. Error Handling
- Always wrap errors with context using
fmt.Errorf - Use custom error types for domain-specific errors
- Never ignore errors in production code
- Log errors appropriately (Zap for structured logging)
3. Concurrency
- Use goroutines for concurrent operations
- Always manage goroutines with channels or sync.WaitGroup
- Use context for cancellation and timeouts
- Avoid shared mutable state when possible
4. Database Operations
- Always use context with timeout for database operations
- Use transactions for multi-step operations
- Implement proper indexing for query performance
- Use GORM's prepared statements to prevent SQL injection
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.
- today First seen · 142 lines · 32 tokens per session scan A 5c37066cc1e4
golang-backend-engineer is an agent published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,192 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-10-17.
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.
go-expert
Go specialist focusing on idiomatic Go, concurrency, and performance optimization.
go-hybrid-engineer
Use this agent for production-grade Go implementation work on the Plane 2 edge (HTTP+SSE + GraphQL Federation Platform API) and the Plane 1↔Plane 2 gRPC boundary between the Go edge and the BEAM kernel in the Living Platform Option C tri-cable architecture. This agent owns the smart-agents Go codebase (retention +…
go-fiber-architect
Go + Fiber architecture specialist. Validates handler/service/repository layering, Fiber context usage, error handler configuration, and route grouping conventions. Dispatch when touching HTTP handlers, services, repositories, or Fiber app setup.
backend-developer
Use when building or modifying server-side services, REST or GraphQL APIs, background workers, CouchDB data models, or Go microservices. Covers Node.js/TypeScript and Go implementations.
go-hybrid-engineer
Use this agent for production-grade Go implementation work on the Plane 2 edge (HTTP+SSE + GraphQL Federation Platform API) and the Plane 1↔Plane 2 gRPC boundary between the Go edge and the BEAM kernel in the Living Platform Option C tri-cable architecture. This agent owns the smart-agents Go codebase (retention +…