Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/getsentry/sentry-for-ainpx agentmods add skills/getsentry/sentry-for-ai/sentry-sdk-skill-creatorWrote 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/skills/getsentry/sentry-for-ai/sentry-sdk-skill-creator)<a href="https://agentmods.dev/skills/getsentry/sentry-for-ai/sentry-sdk-skill-creator"><img src="https://agentmods.dev/badge/skills/getsentry/sentry-for-ai/sentry-sdk-skill-creator.svg" alt="Measured on agentmods" 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.00067 | $0.03187 |
| Opus 5 | $0.00034 | $0.01594 |
| Sonnet 5 | $0.00013 | $0.00637 |
| Haiku 4.5 | $0.00007 | $0.00319 |
Grade A, and why
sentry-sdk-skill-creator 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 6d 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 — 327 lines — stays where its author put it; the contents beside it link to each section on GitHub.
All Skills > SDK Skill Creator
Create a Sentry SDK Skill Bundle
Produce a complete, research-backed SDK skill bundle — a main wizard SKILL.md plus deep-dive reference files for every feature pillar the SDK supports.
Invoke This Skill When
- Asked to "create a Sentry SDK skill" for a new platform
- Asked to "add support for [language/framework]" to sentry-agent-skills
- Building a new
sentry-<platform>-sdkskill bundle - Porting the SDK skill pattern to a new Sentry SDK
Read
${SKILL_ROOT}/references/philosophy.mdfirst — it defines the bundle architecture, wizard flow, and design principles this skill implements.
Phase 1: Identify the SDK
Determine what you're building a skill for:
# What SDK? What's the package name?
# Examples: sentry-go, @sentry/sveltekit, sentry-python, sentry-ruby, sentry-cocoa
Establish the feature matrix — which Sentry pillars does this SDK support?
| Pillar | Check docs | Notes |
|---|---|---|
| Error Monitoring | Always available | Non-negotiable baseline |
| Tracing/Performance | Usually available | Check for span API |
| Profiling | Varies | May be removed or experimental |
| Logging | Newer feature | Check minimum version |
| Metrics | Newer feature | Check minimum version |
| Crons | Backend only | Not available for frontend SDKs |
| Session Replay | Frontend only | Not available for backend SDKs |
| AI Monitoring | Some SDKs | Usually JS + Python only |
Reference existing SDK skills to understand the target quality level:
ls skills/sentry-*-sdk/ 2>/dev/null
# Read 1-2 existing SDK skills for pattern reference
Phase 2: Research
This is the most critical phase. Skill quality depends entirely on accurate, current API knowledge. Do NOT write skills from memory — research every feature against official docs.
Research Strategy
Spin off parallel research tasks (using the claude tool with outputFile) — one per feature area. Each task should:
- Visit the official Sentry docs pages for that feature
- Visit the SDK's GitHub repo for source-level API verification
- Write thorough findings to a dedicated research file
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 327 lines · 67 tokens per session scan A f8d051fbb291
sentry-sdk-skill-creator is a skill published in the GitHub repository getsentry/sentry-for-ai (258 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 3,187 once invoked, about $0.0003 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 skills, from other repositories
generate-message-template
Generate or modify Nightingale (n9e) alert notification message templates. Use when the user asks to write a notification template, change the message format, add hostname/recovery value/severity, or create DingTalk/Feishu/Lark/email/SMS/voice templates.
ops-troubleshooting
This skill should be used when the user asks to "troubleshoot", "diagnose", "debug alert", "investigate incident", "locate a fault", "investigate an alert", "diagnose a problem", "fix an issue", "check alerts", "analyze alerts", "root cause analysis", "check metrics", "check logs", or discusses…
doc-qa
This skill should be used when the user asks "how-to" or factual questions about Nightingale (n9e) — UI/where-to-click, business groups/subscription rules/mute rules/edge mode, Token usage, notification pipeline, self-healing trigger conditions; OR about categraf input plugin field meanings, metric names, defaults…
notify-rule-copilot
One-stop assistant for creating, editing, copying, and troubleshooting Nightingale (n9e) notify rules (notifyrule). Use it when the user asks to "create a notify rule / add a notification policy / configure how alerts are delivered / edit and adjust a notify rule / tiered notification / route by business group or…
alert-mute-copilot
One-stop assistant for creating, editing, and troubleshooting Nightingale (n9e) alert mute rules (alertmute). Use it when the user asks to "create a mute rule / mute an alert / silence an alert / do-not-disturb during a maintenance window / set up periodic muting / mute every early morning / adjust or extend a mute /…
alert-subscribe-copilot
One-stop assistant for creating, editing, and troubleshooting Nightingale (n9e) alert subscription rules (alertsubscribe). Use when the user asks to "create a subscription rule / subscribe to alerts / forward alert events / CC another team / escalate alerts (notify someone else after N minutes unhandled) / receive…