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 Taoidle/plan-cascade --skill gogit clone --depth 1 https://github.com/Taoidle/plan-cascadeWrote 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/taoidle/plan-cascade/go)<a href="https://agentmods.dev/skills/taoidle/plan-cascade/go"><img src="https://agentmods.dev/badge/skills/taoidle/plan-cascade/go/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/taoidle/plan-cascade/go"><img src="https://agentmods.dev/badge/skills/taoidle/plan-cascade/go.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.00030 | $0.00577 |
| Opus 5.5 | $0.00012 | $0.00231 |
| Sonnet 5.5 | $0.00006 | $0.00115 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
go-best-practices 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 1mo 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.
What it actually says
Go Best Practices
Code Style
| Rule | Guideline |
|---|---|
| Formatter | gofmt or goimports |
| Linter | golangci-lint |
| Naming | Short, clear; avoid stuttering |
| Comments | Godoc for exported items |
Error Handling
| Rule | Guideline |
|---|---|
| Always check | Never ignore errors |
| Wrap context | fmt.Errorf("ctx: %w", err) |
| Sentinel errors | var ErrNotFound = errors.New(...) |
func Load(path string) (*Config, error) {
data, err := os.ReadFile(path)
if err != nil {
return nil, fmt.Errorf("load config %s: %w", path, err)
}
// ...
}
Project Structure
cmd/appname/main.go
internal/config/
internal/service/
go.mod
Concurrency
| Pattern | Usage |
|---|---|
context.Context |
Cancellation, timeouts |
sync.WaitGroup |
Wait for goroutines |
errgroup.Group |
Goroutines with errors |
func Process(ctx context.Context, items []Item) error {
for _, item := range items {
select {
case <-ctx.Done():
return ctx.Err()
default:
if err := process(item); err != nil { return err }
}
}
return nil
}
Anti-Patterns
| Avoid | Use Instead |
|---|---|
| Naked returns | Explicit returns |
panic for errors |
Return errors |
| Large interfaces | Small, focused |
init() |
Explicit init |
Testing (Table-Driven)
func TestParse(t *testing.T) {
tests := []struct{ name, input string; want int; wantErr bool }{
{"valid", "42", 42, false},
{"invalid", "abc", 0, true},
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
got, err := Parse(tt.input)
if (err != nil) != tt.wantErr { t.Errorf("err=%v, want=%v", err, tt.wantErr) }
if got != tt.want { t.Errorf("got=%v, want=%v", got, tt.want) }
})
}
}
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.
- 1mo ago First seen · 96 lines · 30 tokens per session scan A 30a17c4639fe
go-best-practices is a skill published in the GitHub repository Taoidle/plan-cascade (132 stars, last pushed 7mo ago), licensed MIT. It adds 30 tokens to every session and 577 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-08-30.
Other skills, from other repositories
golang-pro
Implements concurrent Go patterns using goroutines and channels, designs and builds microservices with gRPC or REST, optimizes Go application performance with pprof, and enforces idiomatic Go with generics, interfaces, and robust error handling. Use when building Go applications requiring concurrent programming…
functions-development
Build serverless Go or Python functions for Falcon Foundry apps. TRIGGER when user asks to "create a function", "write a serverless function", "build backend logic", runs foundry functions create, or needs help with FDK handler patterns, function testing, or collection integration from functions. Also TRIGGER when…
go-concurrency
Use when writing or reviewing Go concurrency — goroutines, channels, errgroup, context cancellation, or goroutine leaks. Not for sequential idioms (go-core-idioms).
go-core-idioms
Use when writing or reviewing idiomatic sequential Go — error handling, slog logging, generics, interfaces, style. Not for concurrency (go-concurrency).
gopls-mcp
Semantic Go code analysis using gopls — type-aware definitions, references, implementations, call hierarchy, dependency graphs, and rename previews. Use these tools for semantic Go tasks; never fall back to grep — gopls sees types, scopes, and interfaces that text search misses.
plugin-dev
Validate plugin SKILL.md frontmatter and audit hook scripts for silent failures. Run validation to check all plugins pass schema, source path, and frontmatter checks. Run hook audit to detect unhandled errors in shell and Python scripts.