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 skills/alexei-led/architect/tools-gonpx skills add alexei-led/architect --skill tools-gogit clone --depth 1 https://github.com/alexei-led/architectWrote 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/alexei-led/architect/tools-go)<a href="https://agentmods.dev/skills/alexei-led/architect/tools-go"><img src="https://agentmods.dev/badge/skills/alexei-led/architect/tools-go.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.00112 | $0.00979 |
| Opus 5 | $0.00056 | $0.00490 |
| Sonnet 5 | $0.00022 | $0.00196 |
| Haiku 4.5 | $0.00011 | $0.00098 |
Grade A, and why
tools-go 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 6d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go tools
Dependency, semantic, and supply-chain evidence for Go modules. The Go toolchain itself answers most structural questions; goda and go-callvis add graph shape.
Evidence dimensions: dependency, structural, semantic (gopls, staticcheck), security (govulncheck).
When to use
Use when the system map shows go.mod. Pick to the question: package
import/dependency facts (go list, go mod graph), boundary/graph analysis (goda),
semantic refs (gopls), bug/dead-code analysis (staticcheck), known
vulnerabilities (govulncheck), call graph (go-callvis). Use the results to judge
package modularity, dependency direction, coupling, and architecture fitness.
Commands
# Direct imports of a package (structural)
go list -deps ./... | sort -u
go list -f '{{.ImportPath}} {{.Imports}}' ./...
# Module-level dependency graph
go mod graph
# Package boundary / dependency queries (cycles, allowed-deps)
goda graph "./...:all"
goda cycle ./...
# Semantic references via the language server
# Use exposed LSP operations from tools-lsp-tree-sitter; do not invent gopls CLI syntax.
# Static analysis: bugs, unused code, suspicious constructs
staticcheck ./...
# Known vulnerabilities in deps + reachable call paths
govulncheck ./...
# Call graph visualization (DOT)
go-callvis -format dot ./...
Evidence output
Record:
dimension: dependency, structural, semantic, or security.source: Go command, package pattern, build tags/GOOS, and module root.facts: package edges, cycles, diagnostics, call paths, vulnerabilities, or confirmed clean scope.limits: non-building packages, missing tools, build tags, generated code, or uncovered GOOS targets.
Confidence impact
go list/go mod graph/ goda output is direct dependency evidence:tools_used, raisesdependency_graph_healthandboundary_integrityconfidence. Cycles fromgoda cycleare concrete findings.govulncheckis the security/supply-chain dimension; it reports reachable vulnerabilities, which is stronger than a raw advisory match — cite the call path.- An existing goda/staticcheck rule gating CI is an enforced fitness check —
count it toward
architecture_fitness; one you'd recommend is not. - staticcheck's
U1000(unused) is reliable for unexported symbols; reflection and build tags can hide reachability — confirm before scoring.
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.
- 6d ago First seen · 104 lines · 112 tokens per session scan A 17a267994336
tools-go is a skill published in the GitHub repository alexei-led/architect (2 stars, last pushed 1mo ago), licensed MIT. It adds 112 tokens to every session and 979 once invoked, about $0.0006 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
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.
printing-press-polish
Polish a generated CLI to pass verification and become publish-ready. Runs diagnostics (dogfood, verify, scorecard, go vet, gosec), automatically fixes all issues (verify failures, static-analysis findings, dead code, descriptions, README, MCP tool quality), reports the before/after delta, and offers to publish. Use…
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…