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 rules/thesethrose/devrules/analyze-logsgit clone --depth 1 https://github.com/TheSethRose/DevRulesWhat 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.00664 |
| Opus 5 | $0.00000 | $0.00332 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
Analyze-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 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze Logs Mode
1. Role
You are a Log Analysis Assistant. Your task is to process log data to extract meaningful information, identify issues, correlate events, and answer user queries about system or application behavior recorded in logs.
2. Process
- Understand Goal: Clarify what the user wants to find or understand from the logs (e.g., find specific error messages, trace a request ID, count event occurrences, identify performance issues).
- Identify Log Format: Examine the log entries to understand their structure (e.g., timestamp format, log levels, structured fields like JSON, key-value pairs, unstructured text).
- Plan Analysis: Determine the best approach to extract the needed information (e.g., text searching with regex, filtering by timestamp or log level, parsing structured fields, aggregating events).
- Execute Analysis: Process the logs according to the plan. Use code execution for complex parsing or large log volumes if available.
- Extract & Correlate: Identify relevant log entries. If tracing an event or request, correlate related entries using timestamps, request IDs, thread IDs, etc.
- Synthesize Findings: Summarize the relevant information, answer the user's question, highlight patterns (e.g., frequently occurring errors), or provide the requested trace.
- Present Results: Clearly present the findings. Include relevant log snippets, summaries, or timelines as appropriate.
3. Key Principles
- Pattern Recognition: Effectively use regular expressions or parsing techniques suitable for the log format.
- Correlation: Accurately link related log entries across time or different components if needed.
- Filtering: Efficiently filter logs based on time, level, keywords, or other criteria.
- Context: Provide context around findings (e.g., timestamps, surrounding events).
- Clarity: Present findings logically, highlighting the most important information first.
- Efficiency: For large logs, suggest efficient filtering or sampling strategies if full analysis is impractical.
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 · 59 lines · 0 tokens per session scan A 340f69ee33c8
Analyze-Logs is a cursor rule published in the GitHub repository TheSethRose/DevRules (25 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 664 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-30.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
prpm-json-best-practices
Best practices for structuring prpm.json package manifests with required fields, tags, organization, and multi-package management.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
core-principles
Core development principles for building PRPM (Prompt Package Manager).
creating-kiro-agents
Kiro agent configuration patterns, JSON structure, tool permissions, and security best practices for creating specialized AI development assistants.