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 commands/mturac/everything-openai-codex/go-buildgit clone --depth 1 https://github.com/mturac/everything-openai-codexWrote 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/commands/mturac/everything-openai-codex/go-build)<a href="https://agentmods.dev/commands/mturac/everything-openai-codex/go-build"><img src="https://agentmods.dev/badge/commands/mturac/everything-openai-codex/go-build.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 | $0.00006 | $0.00425 |
| Opus 5 | $0.00003 | $0.00212 |
| Sonnet 5 | $0.00001 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
go-build 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
Go Build Command
Fix Go build, vet, and compilation errors: $ARGUMENTS
Your Task
- Run go build:
go build ./... - Run go vet:
go vet ./... - Fix errors one by one
- Verify fixes don't introduce new errors
Common Go Errors
Import Errors
imported and not used: "package"
Fix: Remove unused import or use _ prefix
Type Errors
cannot use x (type T) as type U
Fix: Add type conversion or fix type definition
Undefined Errors
undefined: identifier
Fix: Import package, define variable, or fix typo
Vet Errors
printf: call has arguments but no formatting directives
Fix: Add format directive or remove arguments
Fix Order
- Import errors - Fix or remove imports
- Type definitions - Ensure types exist
- Function signatures - Match parameters
- Vet warnings - Address static analysis
Build Commands
# Build all packages
go build ./...
# Build with race detector
go build -race ./...
# Build for specific OS/arch
GOOS=linux GOARCH=amd64 go build ./...
# Run go vet
go vet ./...
# Run staticcheck
staticcheck ./...
# Format code
gofmt -w .
# Tidy dependencies
go mod tidy
Verification
After fixes:
go build ./... # Should succeed
go vet ./... # Should have no warnings
go test ./... # Tests should pass
IMPORTANT: Fix errors only. No refactoring, no improvements. Get the build green with minimal changes.
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 · 88 lines · 6 tokens per session scan A b25baf61e80c
go-build is a command published in the GitHub repository mturac/everything-openai-codex (89 stars, last pushed 10d ago), licensed MIT. It adds 6 tokens to every session and 425 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
research
Research a technical or product question.
selfloop
Start or control a persistent SIPS loop whose only objective is improving SIPS and the agent operating it through measured, verified iterations.
dev-planner
Generate or update DEV-PLAN.md with phased development plan from Product-Spec.md.
patterns
Show the full agentpatterns report — success rate, approach→outcome correlation, top patterns.
verify
Spawn a fresh-context verifier subagent to check completed work against its specification before trusting it.