Borrowing it
Nothing to install: this file belongs to ascii766164696D/log-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ascii766164696D/log-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/ascii766164696D/log-mcpWrote 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/instructions/ascii766164696d/log-mcp/claude-md)<a href="https://agentmods.dev/instructions/ascii766164696d/log-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ascii766164696d/log-mcp/claude-md/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/instructions/ascii766164696d/log-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/ascii766164696d/log-mcp/claude-md.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.01187 | $0.01187 |
| Opus 5 | $0.00593 | $0.00593 |
| Sonnet 5 | $0.00237 | $0.00237 |
| Haiku 4.5 | $0.00119 | $0.00119 |
Grade A, and why
log-mcp CLAUDE.md 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 11d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project overview
log-mcp is an MCP server that gives LLMs tools for analyzing log files without loading them into context. It auto-detects log formats, normalizes variable parts for pattern matching, and provides overview/search/compare/error-analysis tools.
Build & test
uv run pytest # run all tests
uv run pytest -v # verbose
uv run log-mcp # start the MCP server (stdio transport)
No build step — uv run handles everything via pyproject.toml.
Architecture
src/log_mcp/
parsing/ # Format detection + parsers (JSON, text, adaptive)
tools/ # One module per MCP tool (overview, search, segment, stats, errors, compare)
normalize.py # Pattern normalization (UUIDs, hex, IPs, numbers → placeholders)
server.py # FastMCP server setup, registers all tools
util.py # Shared helpers (file validation, time parsing)
Detection order: JSON → TextLogParser (hardcoded patterns) → AdaptiveTextParser (timestamp anchor discovery) → fallback.
What could be improved
These are genuine gaps I noticed while building and testing against real log files — not speculative wishlist items.
Parser gaps
-
Zookeeper/Log4j embedded levels. Lines like
2017-... - INFO [main:ZooKeeper@...] - Session establishedhave the level buried inside the line after a-separator. The text parser doesn't recognize this; all entries getlevel=None. The adaptive parser could learn this pattern but currently doesn't look for- LEVEL [anchors. -
TextLogParser pattern locking is fragile. It locks to the first regex that matches and uses it for the entire file. If a file has a preamble (config dump, banner) before the actual log lines start, it may lock to the wrong pattern and miss everything else.
-
No logfmt support.
key=value key2=value2structured logs (common in Go services) aren't recognized. Would need a dedicated parser. -
No XML/HTML log support. Log4j XML appender output, Windows Event Log exports — these exist in the wild but aren't handled.
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.
- 11d ago First seen · 79 lines · 1,187 tokens per session scan A 174855e2645a
log-mcp CLAUDE.md is an instructions file published in the GitHub repository ascii766164696D/log-mcp (100 stars, last pushed 6mo ago), licensed MIT. It adds 1,187 tokens to every session, about $0.0059 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.