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/capacitygit 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.00732 |
| Opus 5 | $0.00000 | $0.00366 |
| Sonnet 5 | $0.00000 | $0.00146 |
| Haiku 4.5 | $0.00000 | $0.00073 |
Grade A, and why
capacity 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
Capacity Planning Analysis
Analyze resource trends and project future capacity needs:
-
Historical Trend Analysis:
- Query key metrics over 24 hours, 7 days, 30 days
- Memory usage trends (system.ram)
- CPU utilization trends (system.cpu)
- Disk space growth (disk.space)
- Network bandwidth trends
- Container resource growth
-
Growth Rate Calculations:
- Calculate daily/weekly/monthly growth rates
- Project when resources will be exhausted
- Identify seasonal patterns
- Account for business growth
-
Resource Utilization:
- Current usage vs total capacity
- Headroom available for spikes
- Time to 80% threshold
- Time to 100% threshold
-
Per-Resource Analysis:
Memory:
- Current: 30.99 GB total, 18 GB used average
- Swap: 99.99% (CRITICAL - no headroom)
- MySQL trend: Spiked from 6.6 GB to 12.9 GB
- Projection: Need 64 GB to handle spikes + growth
CPU:
- Current: 16 cores, ~7% average utilization
- Peaks: Up to 24% during activity
- Capacity: Plenty of headroom
- Projection: No CPU upgrade needed soon
Disk Space:
- /mnt/data/oldserver/mnt/md3: 94% full (WARNING)
- Growth rate: Calculate from historical data
- Days until full: Estimate based on growth
- Action needed: Cleanup or expansion
Network:
- Primary interface bandwidth usage
- WireGuard VPN traffic
- Container network patterns
- Capacity planning for traffic growth
-
Container Resource Forecasts:
- MySQL memory needs (current 6.6 GB baseline)
- PHP application growth
- maybach service trends
- New services planned
-
Cost Analysis (if applicable):
- RAM upgrade: 32 GB → 64 GB
- Disk expansion costs
- Separate database server option
- Cloud vs on-premises comparison
-
Recommendations Timeline:
Immediate (Now - 1 week):
- Address swap crisis
- Free disk space
- Optimize MySQL configuration
Short-term (1-4 weeks):
- Plan memory upgrade
- Implement monitoring thresholds
- Schedule maintenance windows
Medium-term (1-3 months):
- RAM upgrade execution
- Database server separation planning
- Capacity monitoring automation
Long-term (3-12 months):
- High-availability architecture
- Load balancing implementation
- Multi-node infrastructure
-
Capacity Thresholds:
- Set alerts at 70%, 80%, 90% for each resource
- Define action plans for each threshold
- Establish escalation procedures
-
What-If Scenarios:
- 20% traffic increase impact
- 50% user growth impact
- New service additions
- Disaster recovery needs
Generate report including:
- Executive summary with key findings
- Resource-by-resource analysis
- Growth projections with charts
- Investment recommendations
- Risk assessment
- Timeline for action items
Save to reports/capacity-planning-YYYY-MM-DD.md
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 · 105 lines · 0 tokens per session scan A 48416b5e6424
capacity is a command published in the GitHub repository danielbodnar/skills (2 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 732 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
git
Git operations with intelligent commit messages and workflow optimization.
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.