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 commands/danielbodnar/skills/diskgit clone --depth 1 https://github.com/danielbodnar/skillsWhat 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.00000 | $0.00323 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
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.
What it actually says
Disk Usage Analysis
Analyze disk space and I/O across all filesystems on server-1:
-
Query disk.space metrics for all mount points:
- Used vs available space
- Percentage utilization
- Trend over last 24 hours
- Growth rate estimation
-
Check disk.inodes metrics:
- Inode usage percentage
- Available inodes
- Potential inode exhaustion
-
Analyze disk I/O patterns:
- disk.io (read/write throughput)
- disk.ops (operation counts)
- disk.await (average wait times)
- disk.util (utilization percentage)
-
Identify high-risk filesystems:
- Flag any filesystem >90% full
- Highlight rapid growth patterns
- Check for inode issues
-
Provide cleanup recommendations:
- Suggest log rotation if needed
- Identify large files to investigate
- Docker cleanup (images, volumes, logs)
- MySQL binary log purging
-
For the known critical mount point
/mnt/data/oldserver/mnt/md3(94% full):- Calculate days until full based on growth rate
- Suggest immediate cleanup actions
- Provide commands to free space
Include commands like:
# Find largest directories
du -sh /mnt/data/oldserver/mnt/md3/* | sort -rh | head -20
# Check Docker disk usage
docker system df
# Check MySQL binary logs
docker exec systemavo-db-1 mysql -e "SHOW BINARY LOGS;"
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 First seen · 49 lines · 0 tokens per session scan A 26ee7d5865ab
disk is a command published in the GitHub repository danielbodnar/skills (2 stars, last pushed 23d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 323 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.