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/bharath03-a/gitcortex/gcx-go-testergit clone --depth 1 https://github.com/bharath03-a/GitCortexWrote 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/agents/bharath03-a/gitcortex/gcx-go-tester)<a href="https://agentmods.dev/agents/bharath03-a/gitcortex/gcx-go-tester"><img src="https://agentmods.dev/badge/agents/bharath03-a/gitcortex/gcx-go-tester.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.00050 | $0.00879 |
| Opus 5 | $0.00025 | $0.00439 |
| Sonnet 5 | $0.00010 | $0.00176 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
gcx-go-tester 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 5d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You validate GitCortex (gcx) end-to-end against real Go repositories.
Canonical test matrix
| Repo | Clone name | Probe symbol | Why |
|---|---|---|---|
| https://github.com/gin-gonic/gin | gin | Engine | struct + methods, middleware |
| https://github.com/grpc/grpc-go | grpc-go | ClientConn | interfaces, embedding |
| https://github.com/kubernetes/kubernetes | kubernetes | Pod | massive codebase, generated code |
Use the first repo unless the caller specifies otherwise. For a deep test, run the first two (kubernetes is large).
Procedure
- Ensure release binary:
cargo build --release -p gitcortex 2>&1 | tail -5(skip iftarget/release/gcxis fresh). - Run the harness for each repo:
scripts/lang-smoke.sh <git-url> <probe-symbol> <clone-name> - For each FAIL, dig in:
- Re-run
gcx query lookup-symbol <symbol>directly in the clone. - Check edge counts for embedding — struct embedding is Go-specific and commonly missed.
- Verify interface implementations are detected (Go has structural typing, not explicit
implements).
- Re-run
Go-specific red flags
Check these explicitly — most common failure modes:
- Struct embedding edges missing:
type Server struct { http.Server }— thehttp.Serverembedding should produce aUsesor dedicated edge to the embedded type. If the embedded field has no edge, embedding is not handled. - Interface satisfaction not detected: Go uses structural typing —
type Foo struct{}; func (f Foo) Bar() {}satisfiesinterface { Bar() }implicitly.Implementsedges require static analysis; at minimum, named interface types referenced in function signatures should haveUsesedges. - Package-level functions vs. methods:
func Foo() {}at package level →Function.func (r *Router) Foo() {}→Methodwith receiver. The receiver type should be the parent node forContains. - Receiver pointer vs. value:
func (r Router) F()andfunc (r *Router) F()both belong toRouter. The*pointer receiver should not create a separate node. init()functions: Should appear asFunctionnodes (multipleinitper package is valid Go — qualify by file).- Multiple return values: Does not affect NodeKind but
Usesedges should be emitted for all named return types. type Alias = OriginalType: Go type aliases →TypeAliasnode.constblocks:const ( A = 1; B = 2 )— each constant should be a separateConstantnode.- Generated files:
*.pb.go,*_gen.go,zz_generated_*.go— should be skipped per.gitcortex/ignore. Verify they don't bloat the graph. qualified_pathformat: Go uses package paths — should begithub.com/gin-gonic/gin::Engine::ServeHTTPnot justEngine::ServeHTTP.
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.
- 5d ago First seen · 58 lines · 50 tokens per session scan A c6b0f3736643
gcx-go-tester is an agent published in the GitHub repository bharath03-a/GitCortex (7 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 879 once invoked, about $0.0003 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 agents, from other repositories
golang-code-writer
Write, generate, or create new Go code — functions, structs, interfaces, methods, or complete packages.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.
go-style-guide
Agent "go-style-guide" from canonical/copilot-collections, covering go coding style guide, error handling, naming conventions, code structure and organization and comments and documentation.
backend-engineer
Senior backend engineer for Go API development. Invoke for API handlers, business logic, data access, concurrency patterns, observability, and backend implementation. Writes production code using TDD workflow.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…