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.
git clone --depth 1 https://github.com/rohittcodes/claude-plugin-suiteWrote 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/commands/rohittcodes/claude-plugin-suite/monitor)<a href="https://agentmods.dev/commands/rohittcodes/claude-plugin-suite/monitor"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/monitor/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rohittcodes/claude-plugin-suite/monitor"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/monitor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00006 | $0.00405 |
| Opus 5.5 | $0.00002 | $0.00162 |
| Sonnet 5.5 | $0.00001 | $0.00081 |
| Haiku 4.5 | $0.00001 | $0.00040 |
Grade A, and why
monitor 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 1mo 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
System Monitoring Command
Monitor system health, performance metrics, and operational status with comprehensive analysis.
Context
- Monitor type: $1 (health|performance|errors|all - default: all)
- Time range: $2 (1h|6h|24h|7d - default: 24h)
- System status: !
ps aux | head -10 - Disk usage: !
df -h - Memory usage: !
free -h
Monitoring Analysis
1. System Health Check
- Service status and availability
- Resource utilization (CPU, memory, disk)
- Network connectivity and latency
- Database connection and performance
2. Performance Metrics
- Response times and throughput
- Error rates and success rates
- Queue depths and processing times
- Cache hit rates and efficiency
3. Error Analysis
- Error frequency and patterns
- Critical error identification
- Performance degradation detection
- Anomaly detection and alerting
4. Operational Status
- Deployment status and version
- Configuration validation
- Security posture assessment
- Compliance status check
Monitoring Thresholds
- CPU Usage: < 80%
- Memory Usage: < 85%
- Disk Usage: < 90%
- Response Time: < 500ms (p95)
- Error Rate: < 1%
Expected Outcome
- Comprehensive system health report
- Performance metrics and trends
- Error analysis and recommendations
- Operational status summary
Alert Conditions
Immediate attention required for:
- Critical service failures
- Performance degradation > 50%
- Security incidents or breaches
- Resource exhaustion warnings
Recommendations
Based on monitoring data:
- Performance optimization opportunities
- Capacity planning suggestions
- Infrastructure scaling recommendations
- Preventive maintenance actions
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.
- 1mo ago First seen · 69 lines · 0 tokens per session scan A 3aad746dcc23
monitor is a command published in the GitHub repository rohittcodes/claude-plugin-suite (29 stars, last pushed 1y ago), licensed MIT. It adds 6 tokens to every session and 405 once invoked, about $0.0000 per session on Opus 5.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-21.
monitor compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| monitorrohittcodes/claude-plugin-suite | Command | 29 | 1y ago | MIT | A | 6 | Claude Code |
| checklistgithub/spec-kit | Command | 150k | 3d ago | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 150k | 3d ago | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 150k | 3d ago | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 150k | 3d ago | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 150k | 3d ago | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 150k | 3d ago | MIT | A | 14 | Claude Code |