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/certinia/debug-log-analyzer-mcp/claude-mdgit clone --depth 1 https://github.com/certinia/debug-log-analyzer-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/certinia/debug-log-analyzer-mcp/claude-md)<a href="https://agentmods.dev/instructions/certinia/debug-log-analyzer-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/certinia/debug-log-analyzer-mcp/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.02521 | $0.02521 |
| Opus 5 | $0.01260 | $0.01260 |
| Sonnet 5 | $0.00504 | $0.00504 |
| Haiku 4.5 | $0.00252 | $0.00252 |
Grade A, and why
debug-log-analyzer-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 4d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is the Apex Log MCP Server - a Model Context Protocol (MCP) server for Apex Log Analysis. It provides AI agents with tools to analyze Salesforce Apex debug logs for performance bottlenecks and optimization opportunities.
Development Commands
# Install dependencies
pnpm install
# Build the TypeScript project
pnpm run build
# Development with watch mode
pnpm run dev
# Run the server standalone
pnpm start
Architecture
Core Components
-
src/index.ts: CLI entry point (
bin) — parses flags, constructs and runs the server -
src/server.ts: Main MCP server implementation (
createApexLogServer,runStdioServer,parseServerConfig)- Implements 4 MCP tools:
apexlog_list_slow_operations,apexlog_get_summary,apexlog_list_limit_risks,apexlog_execute_anonymous - Uses stdio transport for communication
- Handles file validation, log parsing, analysis, and anonymous Apex execution
- Implements 4 MCP tools:
-
src/tools/responseShaping.ts: Shared helpers for keeping responses lean —
omitEmpty,toLimitRows,toNamespaceLimitRows,roundMs,roundPercent,NS_TO_MS -
src/tools/apexLogSource.ts: The one way the three analysis tools get a log —
loadApexLog(reads and parses, caching the last parse by path and a fingerprint of everything a stat can see — inode, size, and modification and change time in nanoseconds, so acp -pthat keeps the modification time still misses; the file is opened once and both the stat and the read go to that handle, so nothing can put a different file at the path between the two; the slot holds the in-flight promise, so concurrent callers share one parse and a failed read is not kept; it is dropped five minutes after its last use, on anunrefed timer, because a parsed log holds four to five times the size of the file) andwalkLog -
src/ApexLogParser.ts: Complex log parsing engine (33k+ tokens)
- Exports
parse()function andApexLogParserclass - Handles Apex debug log format parsing into structured data
- Tracks governor limits, performance metrics, and log issues
- Exports
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.
- 4d ago First seen · 111 lines · 2,521 tokens per session scan A be6368dffa36
debug-log-analyzer-mcp CLAUDE.md is an instructions file published in the GitHub repository certinia/debug-log-analyzer-mcp (17 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 2,521 tokens to every session, about $0.0126 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
LogLead CLAUDE.md
Instructions for EvoTestOps/LogLead, covering claude.md, project overview, environment setup, common commands and architecture.
salesforce-mcp-lib CLAUDE.md
Instructions for Damecek/salesforce-mcp-lib, covering salesforce-mcp-lib development guidelines, active technologies, project structure, commands and code style.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.
openrouter-mcp-multimodal AGENTS.md
AGENTS.md instructions for stabgan/openrouter-mcp-multimodal, covering agent instructions, before you ship, releasing (read this before publishing), short version and version files (must all match package.json).
intervals-icu-mcp CLAUDE.md
Instructions for hhopke/intervals-icu-mcp, covering claude.md, project overview, development commands, architecture (quick reference) and tool categories.
ai-toolkit AGENTS.md
AGENTS.md instructions for pipefy/ai-toolkit, covering repository guidelines, documentation map, project structure, import namespace migration: pipefysdk → pipefy and src/pipefysdk/init.py (transitional shim).