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.
git clone --depth 1 https://github.com/getsentry/toolkitWrote 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/commands/getsentry/toolkit/issue)<a href="https://agentmods.dev/commands/getsentry/toolkit/issue"><img src="https://agentmods.dev/badge/commands/getsentry/toolkit/issue/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/commands/getsentry/toolkit/issue"><img src="https://agentmods.dev/badge/commands/getsentry/toolkit/issue.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.00000 | $0.03886 |
| Opus 5.5 | $0.00000 | $0.01554 |
| Sonnet 5.5 | $0.00000 | $0.00777 |
| Haiku 4.5 | $0.00000 | $0.00389 |
Grade A, and why
issue 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 yesterday.
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- yesterday First seen · 421 lines · 0 tokens per session scan A 4512a7ec808c
issue is a command published in the GitHub repository getsentry/toolkit (929 stars, last pushed today), with no licence file. It costs nothing until one of its globs matches a file; then it loads 3,886 tokens. 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-10-14.
Other commands, from other repositories
issue
Command "issue" from getsentry/sentry-mcp, covering examples, list issues, list issues in a specific project, all projects in an org and search for a project across organizations.
local
Command "local" from getsentry/sentry-mcp, covering examples, start the server and tail events (default), run your app with the local server auto-enabled, use a custom port and only show errors and logs (filter out transactions).
fix-issues
Pick up one approved task, implement the fix, and close it.
debug-files
Command "debug-files" from getsentry/sentry-mcp, covering examples, inspect a debug information file (auto-detects the format), bundle jvm sources with a debug id, exclude additional directories and output as json.
architecture-review
Architecture + code-health audit — module boundaries, then fallow on TS/JS — and a task per finding.
event
Command "event" from getsentry/sentry-mcp, covering examples, sending events, send an error event (default level), specify level, release, and environment and add tags and extra data.