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 skills/projanvil/mindforge/go-developmentnpx skills add ProjAnvil/MindForge --skill go-developmentgit clone --depth 1 https://github.com/ProjAnvil/MindForgeWhat 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.00060 | $0.02098 |
| Opus 5 | $0.00030 | $0.01049 |
| Sonnet 5 | $0.00012 | $0.00420 |
| Haiku 4.5 | $0.00006 | $0.00210 |
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 yesterday.
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 — 295 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.
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.
- yesterday 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 5mo ago), licensed MIT. It adds 60 tokens to every session and 2,098 once invoked, about $0.0003 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 skills, from other repositories
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…
client-scripts
Write ServiceNow client scripts (onLoad/onChange/onSubmit/onCellEdit) using gform, guser, GlideAjax, field visibility/mandatory toggles, and validation with debounced server calls.
agoragentic-transaction-assurance
Prepare, evaluate, and reconcile autonomous agent transactions without self-granting payment or owner authority. Use when an agent must bind principal authority, seller terms, payment evidence, execution, delivered outcome, and reconciliation; handle paid retries safely; or prepare an authority request for owner…
linkding
Manage bookmarks with Linkding. Use when the user asks to "save a bookmark", "add link", "search bookmarks", "list my bookmarks", "find saved links", "tag a bookmark", "archive bookmark", "check if URL is saved", "list tags", "create bundle", or mentions Linkding bookmark management.
debugging-mutations
Verify what changed on a ServiceNow instance after a tool call — sysaudit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.
maya-shot-export
Pipeline stage — shot-level export: frame ranges, cameras, FBX / Alembic packaging for editorial. Use when packaging shot data for downstream departments. Not for full pipeline publish (maya-pipeline) or scene assembly (maya-scene-assembly).