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/logs)<a href="https://agentmods.dev/commands/rohittcodes/claude-plugin-suite/logs"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/logs/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/logs"><img src="https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/logs.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.00008 | $0.00524 |
| Opus 5.5 | $0.00003 | $0.00210 |
| Sonnet 5 | $0.00002 | $0.00105 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
logs 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enterprise Log Analysis
Analyze system logs for troubleshooting, monitoring, and security analysis.
Context
- Recent system logs: !
journalctl --no-pager -n 100 --since "1 hour ago" - Application logs: !
tail -n 50 /var/log/application.log 2>/dev/null || echo "Application logs not found" - Error logs: !
grep -i error /var/log/syslog 2>/dev/null | tail -20 || echo "No recent errors found" - Security logs: !
grep -i "failed\|denied\|unauthorized" /var/log/auth.log 2>/dev/null | tail -10 || echo "No security events found" - Web server logs: !
tail -n 20 /var/log/nginx/access.log 2>/dev/null || tail -n 20 /var/log/apache2/access.log 2>/dev/null || echo "Web server logs not found"
Your task
Based on the log information above, provide a comprehensive log analysis including:
-
Log Summary
- Total log entries analyzed
- Log levels distribution (ERROR, WARN, INFO, DEBUG)
- Time range covered
- Key patterns and trends
-
Error Analysis
- Critical errors requiring immediate attention
- Warning patterns and trends
- Error frequency and impact assessment
- Root cause analysis for recurring issues
-
Security Analysis
- Failed authentication attempts
- Unauthorized access attempts
- Suspicious activity patterns
- Security event correlation
-
Performance Analysis
- Response time patterns
- Resource usage spikes
- Performance bottlenecks
- Capacity planning insights
-
Recommendations
- Immediate actions for critical issues
- Log monitoring improvements
- Alert configuration suggestions
- Troubleshooting guidance
Arguments
service: Specific service logs to analyze (optional)level: Log level filter (error, warn, info, debug, optional)timeframe: Time range for analysis (1h, 6h, 24h, 7d, optional)
Usage Examples
/logs
/logs database error
/logs api warn 24h
/logs security 7d
Focus on enterprise-grade log analysis with actionable insights for system reliability, security, and performance optimization.
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.
- 7d ago First seen · 65 lines · 0 tokens per session scan A 7c18f7054e4a
logs is a command published in the GitHub repository rohittcodes/claude-plugin-suite (29 stars, last pushed 11mo ago), licensed MIT. It adds 8 tokens to every session and 524 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.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.