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 dayfinggg/openai-codex-agent-skills --skill go-changegit clone --depth 1 https://github.com/dayfinggg/openai-codex-agent-skillsWrote 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/dayfinggg/openai-codex-agent-skills/go-change)<a href="https://agentmods.dev/skills/dayfinggg/openai-codex-agent-skills/go-change"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/go-change/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/dayfinggg/openai-codex-agent-skills/go-change"><img src="https://agentmods.dev/badge/skills/dayfinggg/openai-codex-agent-skills/go-change.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.00031 | $0.00338 |
| Opus 5.5 | $0.00012 | $0.00135 |
| Sonnet 5.5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
go-change 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.
What it actually says
Preserve Go package contracts and verify concurrency along executed paths.
- Identify the toolchain, go.mod requirements, workspace, build tags, and existing check commands. Read callers and the project's error conventions.
- Trace context.Context from the request boundary through I/O. Identify cancellation, deadline, and resource ownership. Do not substitute a background context merely to bypass cancellation.
- For every new goroutine, establish its termination condition and who joins or observes it. Check blocked channel sends, receives, and early consumer exit. Preserve the established channel-ownership contract.
- Inspect shared maps, slices, and structures. Use the smallest synchronization mechanism with clear ownership. An absence of panic does not prove an absence of races.
- Verify response-body, file, transaction, and cursor cleanup on success and failure. Preserve error wrapping where callers rely on identity.
- Run formatting, existing static analysis, and affected package tests. For shared-memory or concurrency changes, use go test -race on a supported platform.
- Verify cancellation and termination where relevant. For performance work, compare benchmarks with equivalent inputs and conditions.
The race detector checks executed paths only. A clean run is not proof of all possible interleavings. Do not claim a concurrency fix is verified if the failing path was never exercised.
Consult the Go Race Detector, Context, and Go Modules.
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 · 20 lines · 31 tokens per session scan A 2f7575cc2034
go-change is a skill published in the GitHub repository dayfinggg/openai-codex-agent-skills (8 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 338 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-30.
Other skills, from other repositories
tools-go
Gather Go architecture evidence with go list, go mod graph, goda, gopls, staticcheck, govulncheck, and go-callvis. Use when a Go module needs package graphs, import cycles, dependency direction, package-boundary checks, call/reference facts, dead code, vulnerabilities, or call graphs for modularity and coupling…
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-rust-reverse
Use for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.
go-linters
Add and validate custom Go analysis linters in gh-aw.
stack-trace-go-probe
Internal helper for meta-stack-trace-investigator. Use when a Go panic or stack trace needs Go-specific nil/error checks, go test reproducer guidance, and patch targets.
golang-troubleshooting
Troubleshoot Golang programs systematically - find and fix the root cause. Use when encountering bugs, crashes, deadlocks, races, or unexpected behavior in Go code. Covers debugging methodology, common Go pitfalls, test-driven debugging, pprof setup and capture, Delve, race detection, GODEBUG tracing, and production…