logs

logs is a command for Claude Code from rohittcodes/claude-plugin-suite. It costs 8 tokens per session (524 once invoked), scanned A, original, MIT.

A command for reading and analyzing system, application, web-server, and security logs. Logs are timestamped records that describe what software and servers are doing.

In plain words
What is it for?
Use it to investigate failures, find recurring errors, review failed logins or denied access, examine web requests, and identify likely causes of system problems.
Why use it?
It helps turn large, scattered log files into a summary of errors, warnings, trends, and possible security events. This makes troubleshooting and monitoring less dependent on manually searching text.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to investigate failures, find recurring errors, review failed logins or denied access, examine web requests, and identify likely causes of system problems.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/rohittcodes/claude-plugin-suite/logs
Install

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.

Clone the repo
git clone --depth 1 https://github.com/rohittcodes/claude-plugin-suite

Made for: Claude Code.

Wrote 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.

agentmods badge for logs

README.md
[![agentmods](https://agentmods.dev/badge/commands/rohittcodes/claude-plugin-suite/logs/github.svg)](https://agentmods.dev/commands/rohittcodes/claude-plugin-suite/logs)
Your own site
<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.

agentmods 80×15 button for logs

Your own site · 80×15
<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>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 524 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash 7c18f7054e4a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-28, from the pricing page.

Security

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.

commands/logs.md · 65 lines

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:

  1. Log Summary

    • Total log entries analyzed
    • Log levels distribution (ERROR, WARN, INFO, DEBUG)
    • Time range covered
    • Key patterns and trends
  2. Error Analysis

    • Critical errors requiring immediate attention
    • Warning patterns and trends
    • Error frequency and impact assessment
    • Root cause analysis for recurring issues
  3. Security Analysis

    • Failed authentication attempts
    • Unauthorized access attempts
    • Suspicious activity patterns
    • Security event correlation
  4. Performance Analysis

    • Response time patterns
    • Resource usage spikes
    • Performance bottlenecks
    • Capacity planning insights
  5. 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.

Read the full file on GitHub · 65 lines

Changes

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.

  1. 7d ago First seen · 65 lines · 0 tokens per session scan A 7c18f7054e4a

Subscribe to this mod's changes

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.