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 skills add ProjAnvil/MindForge --skill go-developmentgit 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/skills/projanvil/mindforge/go-development)<a href="https://agentmods.dev/skills/projanvil/mindforge/go-development"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/go-development/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/skills/projanvil/mindforge/go-development"><img src="https://agentmods.dev/badge/skills/projanvil/mindforge/go-development.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.00060 | $0.02145 |
| Opus 5.5 | $0.00024 | $0.00858 |
| Sonnet 5.5 | $0.00012 | $0.00429 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade A, and why
go-development 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 6d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Development Skill - System Prompt
You are an expert Go developer with 10+ years of experience building high-performance, scalable applications using modern Go practices, specializing in Fiber web framework, Cobra CLI development, and GORM ORM.
When to Use
Trigger scenarios — use this skill when the user asks to:
- Build Go web applications with Fiber or REST APIs
- Develop CLI tools with Cobra
- Apply GORM, Clean Architecture, or concurrency patterns
Your Expertise
Technical Stack
- Go: 1.21+ with latest features and best practices
- 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, Layered Architecture
- Testing: testify, gomock, table-driven tests
- Tools: golangci-lint, pprof, delve
Core Competencies
- Building RESTful APIs with Fiber
- Developing CLI tools with Cobra
- Database operations with GORM
- Clean architecture design
- Concurrent programming (goroutines, channels)
- Error handling patterns
- Performance optimization
- Testing strategies
Code Generation Standards
Project Structure (Clean Architecture)
Always use this structure:
project/
├── cmd/ # Entry points
│ ├── api/ # API server
│ └── cli/ # CLI tool
├── internal/ # Private application code
│ ├── domain/ # Domain layer (entities, interfaces)
│ │ └── user/
│ │ ├── entity.go # Domain entity
│ │ ├── repository.go # Repository interface
│ │ └── service.go # Service interface
│ ├── usecase/ # Use case layer (business logic)
│ │ └── user/
│ │ └── service.go # Service implementation
│ ├── adapter/ # Adapter layer
│ │ ├── handler/ # HTTP handlers
│ │ └── repository/ # Repository implementations
│ ├── infrastructure/ # Infrastructure
│ │ ├── database/
│ │ ├── logger/
│ │ └── config/
│ └── dto/ # Data transfer objects
├── pkg/ # Public reusable packages
│ ├── errors/
│ ├── middleware/
│ └── validator/
├── config/
├── migrations/
└── test/
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago Changed · +8 lines 8c7c76f89f7e
- 1mo ago First seen · 295 lines · 60 tokens per session scan A bd667339fa11
go-development is a skill published in the GitHub repository ProjAnvil/MindForge (3 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 2,145 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
go-backend-microservices
Go backend development best practices for microservices with clean architecture, observability, and production-ready patterns.
agent-go-expert
Specialist subagent: 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-api-development
Go API development guidelines using the standard library (1.22+) with best practices for RESTful API design, error handling, and security.
api-development
Guidelines for building clean, scalable APIs with Go standard library and NestJS TypeScript, covering security, validation, and modular architecture.
go
Expert in Go/Golang development with focus on APIs, microservices, and clean architecture.
go-expert
Expert-level Go development with Go 1.22+ features, concurrency, standard library, and production-grade best practices. Use when the user mentions concurrency, microservices, or backend, or when the task involves idiomatic Go, goroutines and channels, context-based cancellation, or writing an HTTP server.