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 instructions/skromesch/mcplogview/claude-mdgit clone --depth 1 https://github.com/skromesch/mcplogviewWrote 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/skromesch/mcplogview/claude-md)<a href="https://agentmods.dev/instructions/skromesch/mcplogview/claude-md"><img src="https://agentmods.dev/badge/instructions/skromesch/mcplogview/claude-md.svg" alt="Measured on agentmods" 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 | $0.00440 | $0.00440 |
| Opus 5 | $0.00220 | $0.00220 |
| Sonnet 5 | $0.00088 | $0.00088 |
| Haiku 4.5 | $0.00044 | $0.00044 |
Grade A, and why
mcplogview 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 3d 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.
What it actually says
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
@AGENT.md
Commands
npm run build # TypeScript compile → dist/
npm run dev # Run directly with tsx (no build step needed)
npm test # vitest run (unit + integration)
Portable build (Node.js SEA):
npm run portable:build # produces dist/portable/
npm run portable:verify # smoke-test the binary
npm run portable:checksums
Critical: stdio transport
In stdio mode, only valid MCP JSON-RPC may go to stdout. All debug output, warnings, and errors must go to stderr or logging.path. Writing anything else to stdout breaks MCP clients silently.
Config
LOG_SOURCES_CONFIGenv var sets the config file path (default:config/log-sources.json)config/log-sources.jsonis gitignored — copy fromconfig/log-sources.example.json- If the config file is missing, the server auto-creates a minimal debug config with self-log enabled
SSH sources
SSH tailing spawns ssh as a subprocess with BatchMode=yes (non-interactive). No SSH library is used. identityFile is passed via -i.
Skill files
Optional per-source skills live in config/log-skills/<sourceId>.md (frontmatter + markdown body). The mcplogview-self skill is built-in and not file-loaded.
MCP tools
| Tool | Purpose |
|---|---|
list_logs |
Lists configured sources with labels and hints |
get_log_skill |
Returns structured + markdown skill for a source |
read_log_chunk |
Returns lines + next cursor (cursor-based paging) |
follow_log |
Short-polls for new lines until timeout |
Recommended agent flow: list_logs → get_log_skill → read_log_chunk / follow_log.
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.
- 3d ago First seen · 51 lines · 440 tokens per session scan A 0d10f41dee18
mcplogview CLAUDE.md is an instructions file published in the GitHub repository skromesch/mcplogview (0 stars, last pushed 2mo ago), licensed MIT. It adds 440 tokens to every session, about $0.0022 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-31.
Other instructions, from other repositories
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.