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/lexfrei/ccc/go-cachenpx skills add lexfrei/ccc --skill go-cachegit 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.00081 | $0.00497 |
| Opus 5 | $0.00041 | $0.00249 |
| Sonnet 5 | $0.00016 | $0.00099 |
| Haiku 4.5 | $0.00008 | $0.00050 |
Grade A, and why
go-cache 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.
What it actually says
Reclaim Go cache disk space, then report what was freed.
Operates in report → confirm → execute order. The scope is chosen through an interactive question, not flags. After approval, run the cleanup autonomously.
Step 1: Locate and measure the caches
go env GOCACHE GOMODCACHE
GOCACHEholds the build, test, and fuzz caches — fully regenerated on the next build.GOMODCACHEholds downloaded module sources — re-downloaded on the nextgo build/go mod download. It is usually the largest, often tens of GB.
Measure both: du -sh "$GOCACHE" and du -sh "$GOMODCACHE". If go is not installed, stop and say so.
Step 2: Report and ask (interactive)
Show the size of each cache and the total reclaimable, then ask the user (interactive question) which scope to clear:
- build + test + fuzz only — keeps the module cache, so the next build does not re-download dependencies.
- everything, including the module cache — frees the most, but the next build re-downloads all modules.
Note that either way the next build is slower while caches repopulate.
Step 3: Execute (after approval)
Build, test, and fuzz caches:
go clean -cache -testcache -fuzzcache
Module cache (only if the user chose to include it):
go clean -modcache
go clean -modcache handles the read-only permission bits that Go sets on cached module files — no manual chmod needed.
Step 4: Report
Re-measure GOCACHE and GOMODCACHE and report the space reclaimed, plus what was kept (the module cache, if the user kept it).
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 · 50 lines · 81 tokens per session scan A a4e1bb25aeff
go-cache is a skill published in the GitHub repository lexfrei/ccc (9 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 81 tokens to every session and 497 once invoked, about $0.0004 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
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
layered-architecture-types
Enforce primitive-at-edges / strong-types-in-Business layering and the toBus/fromBusResponse/toDB converter pattern. Use when writing, editing, or auditing Go files under app/, business/domain/, or .../stores/db.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…
golang-observability
Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for…
golang-data-structures
Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing…
golang-dependency-management
Dependency management for Golang projects — go.mod and go.sum, go get install and upgrade flows, Minimal Version Selection, conflict resolution with replace/exclude/retract, govulncheck scanning of the module tree, outdated dependency and binary size auditing, vendoring, tool directives, and go.work workspaces. Use…