# Go Cache

> Reclaim Go disk by clearing the build, test, fuzz, and module caches. Measures each cache first, then cleans the user-chosen scope after approval. TRIGGER when the user wants to free Go cache space ("clean go cache", "почисти go кеши", "reclaim GOMODCACHE"). DO NOT trigger for cleaning a specific module or running go mod tidy.

- **Type:** Skill
- **Install:** `agentstack add skill-lexfrei-ccc-go-cache`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [lexfrei](https://agentstack.voostack.com/s/lexfrei)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** BSD-3-Clause
- **Upstream author:** [lexfrei](https://github.com/lexfrei)
- **Source:** https://github.com/lexfrei/ccc/tree/master/skills/cleanup/skills/go-cache

## Install

```sh
agentstack add skill-lexfrei-ccc-go-cache
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

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

```bash
go env GOCACHE GOMODCACHE
```

- `GOCACHE` holds the build, test, and fuzz caches — fully regenerated on the next build.
- `GOMODCACHE` holds downloaded module sources — re-downloaded on the next `go 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:

```bash
go clean -cache -testcache -fuzzcache
```

Module cache (only if the user chose to include it):

```bash
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).

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [lexfrei](https://github.com/lexfrei)
- **Source:** [lexfrei/ccc](https://github.com/lexfrei/ccc)
- **License:** BSD-3-Clause

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-lexfrei-ccc-go-cache
- Seller: https://agentstack.voostack.com/s/lexfrei
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.