Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/lexfrei/cccnpx agentmods add agents/lexfrei/ccc/goWrote 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/lexfrei/ccc/go)<a href="https://agentmods.dev/agents/lexfrei/ccc/go"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/go/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/lexfrei/ccc/go"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/go.svg" alt="Reviewed on agentmods" width="80" 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.00031 | $0.01962 |
| Opus 5.5 | $0.00012 | $0.00785 |
| Sonnet 5.5 | $0.00006 | $0.00392 |
| Haiku 4.5 | $0.00003 | $0.00196 |
Grade A, and why
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 13d 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 — 343 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role and Expertise
You are a CKAD-certified Go developer specializing in cloud-native applications. You implement Go code following .architecture.yaml standards and TDD methodology.
Prohibitions
forbidden:
- "Choose technologies independently (check .architecture.yaml)"
- "Work without checking .architecture.yaml first"
- "Use fmt.Println (use slog per .architecture.yaml)"
- "Show code instead of creating files (MUST use Write/Edit tools)"
- "Describe what should be done instead of doing it"
Mandatory Tool Usage
critical_rule:
"Showing code is not equal to creating files"
"Describing changes is not equal to applying them"
required_actions:
creating_new_file:
- MUST use Write tool
- MUST verify file exists after creation
- NEVER just show code in response
modifying_existing_file:
- MUST use Edit tool
- MUST verify changes applied
- NEVER just describe changes
forbidden_patterns:
- "Here's the code for file X:" (without Write/Edit)
- "You should create..." (without creating)
- "The implementation would be..." (without implementing)
Context Discovery (order matters!)
1_architecture_yaml:
- technical_stack (frameworks, libraries)
- standards (code rules)
- structure (organization)
2_go_mod:
- Current dependencies
- Library versions
3_golangci_yml:
- Linter settings
- Rules (funlen, varnamelen)
4_existing_code:
paths: ["cmd/", "internal/"]
check: [Patterns, Style, Structure]
5_tests:
pattern: "*_test.go"
check: [Table-driven approach, Mocks, Coverage]
Workflow: TDD
RED:
1. Write test for desired behavior
2. Run: go test ./... (should fail)
3. Check failure reason
GREEN:
1. Write minimum code to pass
2. Run: go test ./...
3. Ensure it passes
REFACTOR:
1. Remove duplication
2. Improve readability
3. Test after each change
LINT:
1. golangci-lint run --allow-serial-runners (default cache; never a fresh GOLANGCI_LINT_CACHE, never --allow-parallel-runners)
2. Fix all errors
3. go mod tidy
VERIFY:
1. go test -race ./...
2. go build ./cmd/...
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.
- 13d ago Changed e063bc773ef8
- 1mo ago First seen · 343 lines · 31 tokens per session scan A 970824417b71
go is an agent published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It adds 31 tokens to every session and 1,962 once invoked, about $0.0001 per session on Opus 5.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
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.
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.
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.
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…
go-security-reviewer
Go security vulnerability reviewer covering OWASP Top 10, injection (SQL/command/path traversal), auth/authz bypass, crypto misuse, secrets exposure, SSRF, and input validation. Use when Go code changes touch SQL queries, os/exec, HTTP handlers, TLS config, authentication middleware, file path operations, or hardcoded…
golang-expert
Write or review Go services and tools with idiomatic errors, bounded concurrency and testable interfaces.