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/tpavanipradeep/everything-claude-code/go-buildgit clone --depth 1 https://github.com/tpavanipradeep/everything-claude-codeWhat 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.00418 |
| Opus 5 | $0.00003 | $0.00209 |
| Sonnet 5 | $0.00001 | $0.00084 |
| 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 2d 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.
This is a copy
100% identical to go-build — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 2d ago First seen · 88 lines · 6 tokens per session scan A 918387886c6d
go-build is a command published in the GitHub repository tpavanipradeep/everything-claude-code (104 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 418 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to go-build, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.