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 skills add nasrulhazim/claude --skill log-monitorgit clone --depth 1 https://github.com/nasrulhazim/claudeWrote 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/skills/nasrulhazim/claude/log-monitor)<a href="https://agentmods.dev/skills/nasrulhazim/claude/log-monitor"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/log-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/skills/nasrulhazim/claude/log-monitor"><img src="https://agentmods.dev/badge/skills/nasrulhazim/claude/log-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00170 | $0.02666 |
| Opus 5 | $0.00085 | $0.01333 |
| Sonnet 5 | $0.00034 | $0.00533 |
| Haiku 4.5 | $0.00017 | $0.00267 |
Grade A, and why
log-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 12d 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 — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Production Log Monitor & Issue Tracker
Analyzes Laravel production log files, categorizes errors, generates structured reports, and creates GitHub issues with proper labels and project board tracking.
Works with: Single log files, daily log directories, or multi-project log collections.
Trigger Detection
Activate when:
- User provides log files or points to a directory containing
.logfiles - User asks to analyze production errors, triage logs, or monitor app health
- User says "check log", "analyze errors", "tengok production", "apa error ni"
Before generating anything:
- Identify all log files — scan the target directory for
*.logfiles - Detect the application — look for Laravel log format (
[YYYY-MM-DD HH:MM:SS] environment.LEVEL:) - Check for existing reports — avoid duplicating previous analysis
- Identify the GitHub repo — check for
.gitremote if issue creation is needed
Analysis Process
Phase 1: Log Discovery
Scan the target directory and identify:
- Log file count and date range
- Total file sizes (to plan reading strategy)
- Any backup files (
.bak,.back.*) that should be included
Phase 2: Error Extraction (Parallel by file)
For each log file, extract:
| Field | Description |
|---|---|
| Timestamp | When the error occurred |
| Level | ERROR, WARNING, CRITICAL, EMERGENCY |
| Exception class | The PHP exception type |
| Message | The error message (first line) |
| Stack trace | Key files/classes involved |
| Context | User IDs, request data, SQL queries |
| Frequency | How many times this exact error appears |
Grouping rules:
- Same exception class + same message = same error (count occurrences)
- Same exception class + different message = separate errors
- Stack trace differences within same error = note variants
Phase 3: Categorization
Assign each unique error to a category:
| Category | Examples |
|---|---|
| Authentication / LDAP | Login failures, LDAP bind errors, OAuth state mismatch |
| Database | Query failures, connection errors, read-only transactions, migrations |
| IAM / Identity Sync | Keycloak sync, AD sync, user provisioning failures |
| Filesystem / Permissions | Permission denied, file not found, storage issues |
| Application Code | Unhandled exceptions, type errors, missing classes |
| Configuration | Missing config, env vars, service container resolution |
| Infrastructure | Memory exhaustion, timeout, queue failures, cache errors |
| Routing / HTTP | Route not found, 404/500 errors, CORS issues |
| External Services | API timeouts, webhook failures, third-party errors |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 370 lines · 170 tokens per session scan A 545cfbca1f80
log-monitor is a skill published in the GitHub repository nasrulhazim/claude (23 stars, last pushed 10d ago), licensed MIT. It adds 170 tokens to every session and 2,666 once invoked, about $0.0009 per session on Opus 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-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.