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/gebruder/wirken/disk-usagenpx skills add gebruder/wirken --skill disk-usagegit clone --depth 1 https://github.com/gebruder/wirkenWrote 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/gebruder/wirken/disk-usage)<a href="https://agentmods.dev/skills/gebruder/wirken/disk-usage"><img src="https://agentmods.dev/badge/skills/gebruder/wirken/disk-usage.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.00011 | $0.00302 |
| Opus 5 | $0.00005 | $0.00151 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
disk-usage 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 4d 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
Disk Usage
Analyze disk space and find what's taking up room.
Overview
- Filesystem usage:
df -h - Current directory:
du -sh . - Subdirectory sizes:
du -sh */ | sort -rh - Top 20 largest dirs:
du -h --max-depth=2 | sort -rh | head -20
Find large files
- Top 20 largest files:
find . -type f -exec du -h {} + | sort -rh | head -20 - Files over 100MB:
find . -size +100M -type f -exec ls -lh {} \; - Files over 1GB:
find . -size +1G -type f -exec ls -lh {} \;
Cleanup candidates
- Old log files:
find /var/log -name "*.gz" -mtime +30 -type f - Core dumps:
find / -name "core.*" -type f 2>/dev/null - Docker:
docker system df(if Docker is installed) - Package cache (apt):
du -sh /var/cache/apt/archives/
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.
- 4d ago First seen · 37 lines · 11 tokens per session scan A 1a9af2ee5eed
disk-usage is a skill published in the GitHub repository gebruder/wirken (169 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 302 once invoked, about $0.0001 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-30.
Other skills, from other repositories
workflow-review
Critically review a Stencila workflow and suggest improvements. Use when asked to review, audit, critique, evaluate, or improve a workflow directory or WORKFLOW.md file. Covers frontmatter validation, DOT pipeline quality, workflow structure, agent selection quality, discovery metadata, ephemeral workflow conventions…
defenseclaw-ops
Manage DefenseClaw enterprise security - scan components, manage tool permissions, view alerts, configure guardrails.
hermes-self-evaluation
Use this skill when the user asks to audit, review, or optimize Hermes's own performance — analyzing session data, skills, configuration, costs, and usage patterns to identify improvements, automation opportunities, and system optimizations.
spec-writing
Spec-writing for Spec-Driven Development (SDD) skill for writing requirement specifications before implementation. Use when starting a new feature, planning work, writing requirements, or designing a component. Trigger keywords: spec, specification, SDD, plan feature, write requirements, design feature, spec-driven…
test-compliance-proxy
End-to-end smoke test for the Compliance Proxy. Use when the user wants to verify that the running compliance-proxy correctly MITM-intercepts HTTPS provider traffic on :3128, applies the compliance pipeline, and writes matching trafficevent rows (source = 'compliance-proxy') plus Prometheus counters. Trigger keywords…
frontend-arch-review
Audit the Control Plane UI + Agent Dashboard against the design-token / CSS framework architecture, including the Tailwind v4 + shadcn surface and the prime-shadcn-tokens.css @theme {} palette. Detects theme/mode-breaking offenders: hex / rgba / hsla literals in .module.css, hex / rgba inside style={{}} blocks in…