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 agents/afshinator/mcp-server-go-quality/referencegit clone --depth 1 https://github.com/afshinator/mcp-server-go-qualityWhat 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.00000 | $0.02134 |
| Opus 5 | $0.00000 | $0.01067 |
| Sonnet 5 | $0.00000 | $0.00427 |
| Haiku 4.5 | $0.00000 | $0.00213 |
Grade A, and why
reference 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 yesterday.
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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reference — mcp-server-go-quality
Detailed error handling, remediation, and troubleshooting. Load on demand when the compact AGENTS.md doesn't cover what you need.
Response schema
Diagnostic {
tool: "golangci-lint" | "govulncheck" | "nilaway"
file: string // relative path from project root; "" if unknown
line: number // 0 if unknown
column: number // absent from JSON when 0 (omitempty)
severity: "error" | "warning" | "" // "" for govulncheck/nilaway; absent when empty
message: string // human-readable summary
error: string // "" on success; non-empty on tool failure
native: object // full raw tool output; also populated for govulncheck parse error diagnostics as a JSON array of error strings
}
Error handling
Tool-level errors (in the Diagnostic array)
These appear as entries with a non-empty error field. Other tools' results are
still present in the same response.
error value |
Meaning | What to do |
|---|---|---|
"Tool command failed with exit code N. Stderr: ..." |
Tool crashed or found a config problem | Show stderr to user; check .golangci.yml or project config |
"timed out after 5m0s" |
Tool exceeded per-tool deadline | Increase timeout in .go-quality.yaml |
"cancelled" |
Client disconnected while tool was running | Safe to retry |
"unexpected output format from <tool>..." |
Tool version mismatch with server's parser | Run install_tools to reinstall the pinned version |
"failed to parse govulncheck output: ..." |
govulncheck output had malformed lines | Likely a govulncheck version issue; run install_tools. Inspect native for the raw parse error. |
Fatal errors (JSON-RPC error, no Diagnostic array)
| Error message | Meaning | What to do |
|---|---|---|
"not a Go project: no go.mod or go.work found" |
No go.mod or go.work walking up from project_path |
Verify the path is inside a Go module |
"config error: ..." |
.go-quality.yaml is malformed or unreadable |
Fix the YAML or delete the file to use defaults |
"unknown tool: \"<value>\". valid values: golangci-lint, govulncheck, nilaway" |
Bad value in tools parameter |
Check the tools array for typos |
"installing <tool>: ..." |
Tool installation failed | Report to user; try running go install <path>@<version> manually |
"...resolving Go binary directory..." |
go is not on PATH |
The Go toolchain must be installed separately; the server will not start |
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.
- yesterday First seen · 209 lines · 0 tokens per session scan A dd28ef9e3c3d
reference is an agent published in the GitHub repository afshinator/mcp-server-go-quality (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,134 tokens. 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 agents, from other repositories
demo-site
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…
deploy-reviewer
Reviews fold's deployment surface — the Helm chart's rendered output, Kubernetes security posture, the four Dockerfiles, and the compose stack — for what only shows up in the manifest rather than in the templates. Use after changes under deploy/, before a chart release, or when auditing how fold actually runs in a…
release-verifier
Verifies a published fold release end to end from the outside — archives, checksums and their cosign signature, SBOMs, the four ghcr images, the OCI chart, and every sigstore attestation. Use after a tag's release workflow goes green, before announcing a release, or when someone asks whether a published artifact is…
CREATING_AGENTS
Station agents are intelligent AI assistants that can execute tasks using MCP (Model Context Protocol) tools. This guide covers creating, configuring, and deploying agents.
station-operator
Station AI agent operator. Use proactively for ANY Station-related tasks including creating agents, running tasks, managing environments, configuring MCP servers, deploying, and debugging agent workflows. Has full access to Station's 55+ MCP tools.
mcp-spec-auditor
Audits fold against the normative MCP specification for the pinned revision — method shapes, required fields and headers, error-code allocation, caching and intermediary rules, and deprecations on the clock. Use when a change touches wire behavior, when a new protocol revision ships, or before bumping the conformance…