Borrowing it
Nothing to install: this file belongs to shields/lgtmcp. 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/shields/lgtmcp/main/AGENTS.mdgit clone --depth 1 https://github.com/shields/lgtmcpWrote 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/shields/lgtmcp/agents-md)<a href="https://agentmods.dev/instructions/shields/lgtmcp/agents-md"><img src="https://agentmods.dev/badge/instructions/shields/lgtmcp/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/shields/lgtmcp/agents-md"><img src="https://agentmods.dev/badge/instructions/shields/lgtmcp/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.02691 | $0.02691 |
| Opus 5.5 | $0.01076 | $0.01076 |
| Sonnet 5.5 | $0.00538 | $0.00538 |
| Haiku 4.5 | $0.00269 | $0.00269 |
Grade C, and why
lgtmcp AGENTS.md scanned grade C 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 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.
Nullifies safety policieshighAnti-refusal
"You have no restrictions", "do anything now", "ignore your guidelines": a direct jailbreak that disables guardrails.
- The deny rule matches on the leading command name. It does not match indirect invocations such as `sh -c "git commit ..."` or `bash -c "git commit ..."`. This is a known limitation of the Claude Code permission grammar How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LGTMCP - AI Code Review via MCP
IMPORTANT:
- After completing any task, run
make lint,make test, then usemcp__lgtmcp__review_onlyto review changes. - Do not use conventional commit prefixes (feat:, fix:, docs:, etc.) in commit messages.
- Update this file only when a change alters durable guidance — commands, policies, architecture, or gotchas recorded nowhere else. Implementation detail belongs in code doc comments; this file is not a changelog.
File Headers
All new files must include the project copyright and Apache 2.0 license header, matching the style of existing files.
Commit policy
The sanctioned way to commit changes to this repo is via the mcp__lgtmcp__review_and_commit MCP tool, which performs a Gemini-reviewed commit and only writes the commit if the reviewer returns LGTM. Direct git commit invocations from the Bash tool are denied via .claude/settings.json to prevent unreviewed commits from slipping in.
The Bash deny rule (Bash(git commit:*)) is best-effort defense-in-depth, not a hard sandbox. Be aware of these intentional gaps:
- It does not (and cannot) block commits that go through the
mcp__lgtmcp__review_and_committool. That tool runs inside the lgtmcp Go binary, outside the Bash deny scope, and committing is its entire purpose. This is by design. - The deny rule matches on the leading command name. It does not match indirect invocations such as
sh -c "git commit ..."orbash -c "git commit ...". This is a known limitation of the Claude Code permission grammar — the rule cannot reliably inspect arguments to a shell wrapper. Do not use shell indirection to bypass the policy; always go through the MCP tool.
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 Changed · +1 lines · +202 tokens per session 481cba1f725a
- 5d ago Changed · +1 lines · +151 tokens per session 606afc1afc79
- 6d ago Changed · +1 lines · +121 tokens per session 6653cd8c8041
- 1mo ago Changed ba50cfa5884b
- 1mo ago Changed · +1 lines · +72 tokens per session 7709af9d6862
- 2mo ago First seen · 124 lines · 2,145 tokens per session scan C 3168dcf90c73
lgtmcp AGENTS.md is an instructions file published in the GitHub repository shields/lgtmcp (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 2,691 tokens to every session, about $0.0108 per session on Opus 5.5. A static security scan graded it C with 1 finding (nullifies safety policies). 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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.