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 skills add getsentry/sentry-for-ai --skill sentry-setup-releasesgit clone --depth 1 https://github.com/getsentry/sentry-for-aiWrote 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-setup-releases)<a href="https://agentmods.dev/skills/getsentry/sentry-for-ai/sentry-setup-releases"><img src="https://agentmods.dev/badge/skills/getsentry/sentry-for-ai/sentry-setup-releases.svg" alt="Measured on agentmods" height="20"></a>- Socket pass
- Snyk warn
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.00090 | $0.01616 |
| Opus 5 | $0.00045 | $0.00808 |
| Sonnet 5 | $0.00018 | $0.00323 |
| Haiku 4.5 | $0.00009 | $0.00162 |
Grade A, and why
sentry-setup-releases 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 7d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- sentry-setup-releases — 100% identical, 0 lines differ
- sentry-setup-releases — 100% identical, 0 lines differ
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.
Set Up Sentry Releases
Without a release, an issue tells you what broke but nothing about when it started or what changed. This skill wires that up end to end: the version tag on events, the release created in CI with its commits and deploy, and the suspect-commit path that turns an issue into a culprit PR.
The whole setup fails silently — every piece can be individually correct while producing nothing visible — so this skill’s real job is to diagnose which piece is missing before configuring anything.
Wrong skill? If Sentry isn’t installed and capturing events yet, start with
sentry-instrument — releases decorate events you already receive.
If the complaint is minified or unsymbolicated frames, that’s sentry-fix-stack-traces
(readable frames are a prerequisite for suspect commits, so you may come back here
after). If the goal is fixing one specific issue rather than setting up the wiring,
that’s sentry-debug-issue. Note that sentry-get-started and sentry-instrument set
the release tag during setup, using the same references — this skill is the entry
point for the CI half and for a release feature that isn’t working.
Step 1 — Establish which half exists before configuring anything
Do not start writing CI config. Most projects arrive here partially set up, and the
fix depends entirely on which half is missing.
Read the diagnosis table in
references/releases/index.md and answer its two
questions:
- Are events tagged? Pull a recent event via the MCP (
search_issues, thenget_sentry_resource) and read itsreleasetag. Note the exact value — you will compare it character for character. - Does the release object exist under that name? This is a different question,
and an event search cannot answer it —
release:<value>only tells you events carry the tag, which you already know from the previous bullet. Callget_release_detailswith that exact version: it returns the commits and deploys attached to the release — deploys with their environment, commits with author and repository — which is what tells you whether the CI half ran. If you don’t have the exact string,find_releaseslists releases with alastCommit/lastDeploysummary on each, enough to see at a glance which ones CI touched. Both are catalog tools and usually aren’t exposed directly — reach them viasearch_sentry_tools/execute_sentry_tool. Also grep the repo for what is already wired: a Sentry bundler plugin in the build config,getsentry/action-releasein a workflow,sentry-cli releasesin a deploy script.
What ships with it
1 file 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.
- 7d ago First seen · 128 lines · 90 tokens per session scan A bc78f9806552
sentry-setup-releases is a skill published in the GitHub repository getsentry/sentry-for-ai (258 stars, last pushed 2d ago), licensed MIT. It adds 90 tokens to every session and 1,616 once invoked, about $0.0005 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
sentry-setup-releases
Set up Sentry releases and deploy tracking — tag events with a version and environment, create the release in CI with its commits, and wire up suspect commits and code mappings, so Sentry can show which release introduced an issue, which commit is responsible, and release health. Use when asked to set up releases…
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.