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/getsentry/sentry-for-ai/agents-mdgit clone --depth 1 https://github.com/getsentry/sentry-for-aiWhat 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.02263 | $0.02263 |
| Opus 5 | $0.01131 | $0.01131 |
| Sonnet 5 | $0.00453 | $0.00453 |
| Haiku 4.5 | $0.00226 | $0.00226 |
Grade A, and why
sentry-for-ai 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 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.
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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Project Overview
Sentry plugin for AI coding assistants (Claude Code, Cursor, Codex, and Grok). Provides MCP server integration and skills.
Commit Attribution
AI commits MUST include:
Co-Authored-By: (the agent model's name and attribution byline)
Repository Structure
All buildable source lives under src/ — this repo is not itself an installable plugin.
src/skills/ # Skill library (source of truth)
src/references/ # Shared reference content hydrated into skills at build time
src/plugins/<agent>/ # Per-agent build scripts + manifests
src/plugins/version.json # The one release version, stamped into every manifest
src/SKILL_TREE.md # Generated skill index (see Skill Tree Navigation below)
Per-agent plugin metadata is generated by the src/plugins/<agent>/build.sh scripts and
published to each agent’s distribution repository; it is not committed here.
Skill frontmatter is name, description, and license. Nothing else is required, and
the retired router fields (category, parent, role, disable-model-invocation) are
rejected — see Skill Tree Navigation below.
Skills
src/SKILL_TREE.md is the list, generated from the skills
themselves.
Read it rather than a copy: an inventory duplicated here goes stale the first
time a skill is added, renamed, or dissolved, which is exactly what happened to the one
that used to live in this section.
The shape to know: every skill is flat and task-shaped — one skill, one job a user
would name, found through its own description. Platform coverage is not a skill per
SDK; the per-platform material lives in the reference library and is hydrated into
whichever skills declare it.
MCP Server
Sentry MCP server configured at https://mcp.sentry.dev/mcp. The source of truth is
mcp.json: Cursor consumes it as-is at the plugin root, while the Codex and Grok builds
emit it as .mcp.json (Codex’s validator requires the dotted name; Grok auto-discovers
it).
Claude declares the server inline in its plugin.json (mcpServers), so the Claude
build ships no MCP file.
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 · 192 lines · 2,263 tokens per session scan A 53918f5b4238
sentry-for-ai AGENTS.md is an instructions file published in the GitHub repository getsentry/sentry-for-ai (255 stars, last pushed 4d ago), licensed MIT. It adds 2,263 tokens to every session, about $0.0113 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
skills AGENTS.md
Instructions for getsentry/skills, covering agent instructions, skill structure, creating/updating skills, registration checklist and key conventions.
dotagents AGENTS.md
Instructions for getsentry/dotagents, covering agent instructions, package manager, what this project is, architecture and principles.
warden-skills AGENTS.md
Instructions for getsentry/warden-skills, covering agent instructions, layout, naming, tooling and skills.
sentry-mcp AGENTS.md
AGENTS.md instructions for getsentry/sentry-mcp, covering agents.md, principles, constraints, repository structure and documentation map.
warden AGENTS.md
AGENTS.md instructions for getsentry/warden, covering agent instructions, package manager, commit attribution, architecture and key conventions.
sentry-mcp CLAUDE.md
Claude Code instructions for getsentry/sentry-mcp, a project described as: An MCP server for interacting with Sentry via LLMs.