Borrowing it
Nothing to install: this file belongs to mudrii/golink. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mudrii/golink/main/.claude/skills/go-rig/SKILL.mdgit clone --depth 1 https://github.com/mudrii/golinkWrote 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/mudrii/golink/go-rig)<a href="https://agentmods.dev/skills/mudrii/golink/go-rig"><img src="https://agentmods.dev/badge/skills/mudrii/golink/go-rig.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.00064 | $0.01699 |
| Opus 5 | $0.00032 | $0.00849 |
| Sonnet 5 | $0.00013 | $0.00340 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade A, and why
go-rig 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 7d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Rig
Process and review discipline for Go work in this repo.
Scope split (do not duplicate across layers):
CLAUDE.md— toolchain, commands, env vars, exit codes, style pointers.claude/rules/go-idioms.md— Go 1.26 idioms and modernizers.claude/rules/go-patterns.md— style, API, docs, and testing patterns- This skill — ATDD/TDD workflow, DI discipline, coverage floors, schema-first, review gate, reject list
If CLAUDE.md is stricter on a shared point, follow CLAUDE.md.
When to use
- implementing a new feature or behavior increment
- refactoring for clearer ownership or testability
- reviewing package boundaries or dependency flow
- replacing hidden collaborator construction with explicit injection
- tightening tests around user-visible or integration behavior
ATDD/TDD workflow
Test-first is a design tool, not an afterthought. Every meaningful behavior change follows red → green → refactor.
- ATDD (acceptance-first) for any user- or agent-visible change — drive from
cmd/command_test.goorcmd/transport_test.goso the test speaks in "what the CLI does", not "what the function does" - TDD (unit-first) for internal invariants, validation rules, and edge cases — drive from a package-local
*_test.go
- Define the boundary behavior you want
- Add/update the closest consumer-level test (ATDD when user-visible; unit otherwise)
- Write the smallest failing assertion for the next increment
- Minimal implementation to pass
- Refactor while green; commit often
- Repeat
If repo policy blocks automatic test execution, still design test-first and ask before running. "Test everything you write" — no behavior ships without at least one consumer-level test pointing at it.
Coverage floors
Measured via go test -cover ./.... Touched packages must meet the floor or the PR must explicitly note the gap.
internal/api,internal/auth,internal/output,cmd/≥ 75%internal/config,internal/mcp≥ 70%- Every branch of
cmd.mapTransportError(401/403/404/422/429/5xx/unknown) has a test - Every
Transportmethod called by the CLI or MCP has an httptest-backed case ininternal/api/official_test.go main.goexempt (pure wiring)
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.
- 7d ago First seen · 166 lines · 64 tokens per session scan A 2e47e98ea191
go-rig is a skill published in the GitHub repository mudrii/golink (5 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 1,699 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
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
golang-testing
Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
go-127
What changed in Go 1.27 (released August 2026) and how it changes the way Go is written in pi-go. Use this skill when writing or reviewing Go that could use a 1.27 feature, when bumping the go directive in go.mod, when a build or test behaves differently after a toolchain upgrade, or when code-guidelines-go points…
bubbletea-testing
Use this skill whenever writing tests for Bubble Tea (charmbracelet/bubbletea) TUI applications in Go. Triggers include any mention of testing Bubble Tea models, teatest, golden file testing for TUIs, testing tea.Cmd or tea.Msg, snapshot testing terminal output, or writing tests for any Go CLI/TUI that uses the Elm…
check-linters-before-commit
Before any commit, run linters, vet, tests, and build verification; do not commit until checks pass.
vite-plus-conventions
vite+ unified TypeScript toolchain conventions: the vp CLI for package/node management, oxlint/oxfmt, type-aware linting, vitest, rolldown/tsdown bundling, task caching, and migration. Load when configuring or reviewing a vite+ TypeScript toolchain.