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/sumithr/sumo-qa/agents-mdgit clone --depth 1 https://github.com/sumithr/sumo-qaWhat 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.01433 | $0.01433 |
| Opus 5 | $0.00717 | $0.00717 |
| Sonnet 5 | $0.00287 | $0.00287 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade B, and why
sumo-qa AGENTS.md scanned grade B with 1 finding 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
| Run the verification call | Anything that requires admin / sudo elevation | How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md, sumo-qa setup
If you're an AI agent setting up sumo-qa for the user, follow this exactly. One command for the common case; per-host flags if you only need to wire one host.
GitHub issue creation
When creating GitHub issues, use the closest template in .github/ISSUE_TEMPLATE/ and include every required field in the issue body. For implementation tasks raised by an AI agent, use .github/ISSUE_TEMPLATE/ai-task.yml unless a more specific template fits better.
Default: configure every detected host
python -m pip install sumo-qa
python -m sumo_qa.installer
pip install sumo-qa creates both sumo-qa (the MCP server binary) and sumo-qa-install (this configurator). Use python -m sumo_qa.installer for setup because it works even when the pip Scripts directory is not on PATH yet.
What sumo-qa-install does:
- Locates the
sumo-qaMCP binary. Ifpip install sumo-qaalready put it on PATH (the common case), uses that path directly: nouvinvocation. Ifsumo-qais not on PATH yet, falls back touv tool installand printsuvinstall instructions ifuvis also missing. - Claude Code (if
~/.claude/exists): symlinks eachskills/<name>/into~/.claude/skills/<name>/. Writesclaude_desktop_config.jsonwith the MCP entry pointing at the absolute binary path. - VS Code + Copilot (if cwd is a workspace with
.git/.vscode/package.json/ etc.): writes.vscode/mcp.jsonwith the VS Code-native schema (serverskey,type: stdio). - JetBrains IDEs (if JetBrains config dir exists): prints exact Settings UI steps. JetBrains' MCP plugin requires Settings UI registration: external XML writes don't reliably register the runtime coroutine.
- Verifies the binary responds to JSON-RPC
initialize.
Per-host flags
Use these when you only want to configure one host:
python -m sumo_qa.installer --claude-code # Claude Code only
python -m sumo_qa.installer --vscode # VS Code workspace (cwd-based)
python -m sumo_qa.installer --vscode --workspace /path/to/repo
python -m sumo_qa.installer --jetbrains # Prints JetBrains UI steps only
python -m sumo_qa.installer --vscode --skip-mcp-install # Skip uv reinstall for speed
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.
- 2d ago First seen · 115 lines · 1,433 tokens per session scan B 66e3571af69b
sumo-qa AGENTS.md is an instructions file published in the GitHub repository sumithr/sumo-qa (6 stars, last pushed 8d ago), licensed Apache-2.0. It adds 1,433 tokens to every session, about $0.0072 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
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).
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.
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).
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.
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.