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/lexfrei/ccc/gogit clone --depth 1 https://github.com/lexfrei/cccWhat 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.00031 | $0.01934 |
| Opus 5 | $0.00015 | $0.00967 |
| Sonnet 5 | $0.00006 | $0.00387 |
| Haiku 4.5 | $0.00003 | $0.00193 |
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 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.
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
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.
- 2d ago First seen · 343 lines · 31 tokens per session scan A 970824417b71
go is an agent published in the GitHub repository lexfrei/ccc (9 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 31 tokens to every session and 1,934 once invoked, about $0.0002 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.