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/fmind/dot/reclaim-disknpx skills add fmind/dot --skill reclaim-diskgit clone --depth 1 https://github.com/fmind/dotWrote 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/skills/fmind/dot/reclaim-disk)<a href="https://agentmods.dev/skills/fmind/dot/reclaim-disk"><img src="https://agentmods.dev/badge/skills/fmind/dot/reclaim-disk.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.00037 | $0.00665 |
| Opus 5 | $0.00018 | $0.00332 |
| Sonnet 5 | $0.00007 | $0.00133 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
reclaim-disk 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 yesterday.
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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reclaim Disk
Free disk space in safety order: the big shared caches first through dot prune, project directories last; dot-cli owns the dot prune flag reference.
Workflow
- Measure:
duffor the filesystem, thendust -d 2 ~anddust -d 1 ~/.cache ~/.local/sharefor the largest directories. - Check for running agents:
pgrep -af "claude|codex|agy|opencode|copilot|grok"; never delete the working directory,.agents/tmp, or session store of a live session. - Preview:
dot prune --dry-run --all=deeplists what the configured targets would remove (agent sessions, Go, uv, npm, mise, Docker, tool caches). - Prune:
dot prune --all=deep, or one target at a time (dot prune --go=module,dot prune --docker=system) when a cache still serves an active project. - Tool-specific extras when still short:
mise prune -y,pnpm store prune,go clean -modcache,uv cache clean,nvim --headless '+Lazy! clean' +qa. - Project directories last:
.venv,node_modules,target,dist,tmpin inactive projects; they rebuild from lockfiles. - Verify and report:
dufagain; list the freed space per target and anything skipped because an agent was using it.
Gotchas
- Never delete keys or secrets:
~/.config/chezmoi/key.txt(the age key),~/.ssh, anysecrets.fishor*.agefile. - Uncommitted work: check
git statusbefore removing anything inside a repository. - Docker volumes:
docker volume lsshows data volumes; remove one only when the user names it. - k3d cluster:
dot prune --docker=systemdeletes stopped k3d clusters; stop and keep the cluster only when the user needs its state.
Documentation
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.
- yesterday Changed 4a1c20b3649e
- yesterday First seen · 37 lines · 37 tokens per session scan A 220d73b1e1fe
reclaim-disk is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 665 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-09-03.
Other skills, from other repositories
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
google-workspace-cli
Use gws across Workspace APIs with schema-first calls, profile isolation, bounded reads, and verified Drive, Docs, Sheets, Gmail, Calendar, or Chat writes.
handover
Write a self-contained follow-up prompt carrying this session's decisions, constraints, and verified findings into a fresh agent session. Use when handing unfinished work to a new context window.
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.