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/skills/agents-mdgit clone --depth 1 https://github.com/getsentry/skillsWhat 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.00479 | $0.00479 |
| Opus 5 | $0.00239 | $0.00239 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
skills 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.
What it actually says
Agent Instructions
Skill Structure
skills/<skill-name>/SKILL.md
skills/<skill-name>/SPEC.md
If you use Claude marketplace sparse checkouts for this repo, include skills and agents alongside .claude-plugin because the root plugin manifest loads repo-root skills/ and agents/.
Creating/Updating Skills
ALWAYS use /skill-writer — it handles requirements, writing, registration, and validation.
- Do not create per-skill alias or symlink skills
- The repo-level
.agents/skillspath is a convenience mirror of canonicalskills/ - List only canonical skills in public skill inventories (for example
pr-writer,skill-writer)
Registration Checklist
- Create
skills/<skill-name>/SKILL.md - Create
skills/<skill-name>/SPEC.md - Add to
README.mdAvailable Skills table (alphabetical by canonical skill name; exclude aliases/symlinks) - Add to
.claude/settings.json:Skill(sentry-skills:<skill-name>) - Add to allowlist in
skills/claude-settings-audit/SKILL.md - For skills with deliberate invocation policy, set Claude's
disable-model-invocationinSKILL.mdand Codex'spolicy.allow_implicit_invocationinagents/openai.yamlto matching behavior
Key Conventions
- Frontmatter
---must be the first line of SKILL.md — no comments before it namefield must match the directory name exactlydescriptionincludes trigger keywords — this is how agents discover the skill- Attribution comments go after the closing
--- - Python scripts: always use
uv run <script>, neverpythonorpython3 - Keep SKILL.md under 500 lines; move reference material to
references/ - Keep runtime instructions in
SKILL.md; put intent, source/evidence model, evaluation, limitations, and maintenance rules inSPEC.md
References
- Skill template and optional fields:
README.md - Testing and PR workflow:
CONTRIBUTING.md - Agent Skills Spec
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 · 39 lines · 479 tokens per session scan A e783846268d6
skills AGENTS.md is an instructions file published in the GitHub repository getsentry/skills (973 stars, last pushed 7d ago), licensed Apache-2.0. It adds 479 tokens to every session, about $0.0024 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
sentry-for-ai AGENTS.md
Instructions for getsentry/sentry-for-ai, covering agent instructions, project overview, commit attribution, repository structure and skills.
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.