Borrowing it
Nothing to install: this file belongs to CraigWetzelberger/sumo-mcp-readonly. 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/CraigWetzelberger/sumo-mcp-readonly/main/AGENTS.mdgit clone --depth 1 https://github.com/CraigWetzelberger/sumo-mcp-readonlyWrote 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/craigwetzelberger/sumo-mcp-readonly/agents-md)<a href="https://agentmods.dev/instructions/craigwetzelberger/sumo-mcp-readonly/agents-md"><img src="https://agentmods.dev/badge/instructions/craigwetzelberger/sumo-mcp-readonly/agents-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/craigwetzelberger/sumo-mcp-readonly/agents-md"><img src="https://agentmods.dev/badge/instructions/craigwetzelberger/sumo-mcp-readonly/agents-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.00769 | $0.00769 |
| Opus 5 | $0.00385 | $0.00385 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
sumo-mcp-readonly AGENTS.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 9d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sumo-mcp-readonly
A read-only MCP server for querying Sumo Logic logs via the Search Job API.
Project Status
Complete and working. All 5 tools functional, 68 unit tests passing.
Tech Stack
- TypeScript, Node.js 20+, ESM
- MCP SDK (
@modelcontextprotocol/sdk) - Zod for input validation
- Vitest for tests
- stdio transport
Key Architecture Decisions
- Timestamps sent as epoch milliseconds (not ISO-8601) to the Sumo API — Sumo rejects ISO format with milliseconds
- Cookies must be maintained per job session (Sumo requirement)
- In-memory job registry tracks jobs created by this process — only owned jobs can be queried/cancelled
- All logs to stderr (stdout reserved for MCP JSON-RPC protocol)
- Credentials never logged — redaction applied before any error output
MCP Tools
sumo_search_logs— Run arbitrary Sumo queriessumo_find_errors— Opinionated error search (ERROR, exception, failure, fatal, stack traces)sumo_search_correlation_id— Search for a trace/request/correlation IDsumo_get_search_status— Poll a running search jobsumo_cancel_search— Cancel a running search job
Configuration
Environment variables loaded via --env-file=.env in npm start, or passed via MCP client config env block.
Required:
SUMO_ACCESS_IDSUMO_ACCESS_KEYSUMO_API_BASE_URL— Regional API endpoint (see README for full list)
Sumo Logic API Reference
POST /v1/search/jobs— Create job (body:{ query, from, to, timeZone })GET /v1/search/jobs/{id}— Poll statusGET /v1/search/jobs/{id}/messages?offset=X&limit=Y— Get messagesGET /v1/search/jobs/{id}/records?offset=X&limit=Y— Get recordsDELETE /v1/search/jobs/{id}— Cancel/delete job- Auth: HTTP Basic (AccessID:AccessKey)
- Rate limit: 4 req/s, 200 concurrent jobs per org
Build & Test
npm install
npm run build # TypeScript compile
npm test # Unit tests
npm run lint # ESLint
npm start # Requires .env file
Project Structure
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.
- 9d ago First seen · 89 lines · 769 tokens per session scan A d1821ae23fe5
sumo-mcp-readonly AGENTS.md is an instructions file published in the GitHub repository CraigWetzelberger/sumo-mcp-readonly (1 stars, last pushed 1mo ago), licensed MIT. It adds 769 tokens to every session, about $0.0038 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
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.