What is investigate-sentry-issue?

A procedure for investigating and classifying an error recorded in Sentry, a service that collects application errors and their diagnostic details. It gathers issue metadata, stack traces, breadcrumbs, tags, and context.

Use it with a Sentry issue ID or URL to inspect when the error occurred, how often it happened, affected environments, and the actions and code path leading to it.

It turns a reported error into enough technical context to decide whether and how it should be fixed.

investigate-sentry-issue — Command for Claude Code by desplega-ai

Install

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.

Clone the repo

git clone --depth 1 https://github.com/desplega-ai/agent-swarm

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/desplega-ai/agent-swarm/investigate-sentry-issue/github.svg)](https://agentmods.dev/commands/desplega-ai/agent-swarm/investigate-sentry-issue)

Your own site

<a href="https://agentmods.dev/commands/desplega-ai/agent-swarm/investigate-sentry-issue"><img src="https://agentmods.dev/badge/commands/desplega-ai/agent-swarm/investigate-sentry-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/desplega-ai/agent-swarm/investigate-sentry-issue"><img src="https://agentmods.dev/badge/commands/desplega-ai/agent-swarm/investigate-sentry-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 596 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00010	$0.00596
Opus 5	$0.00005	$0.00298
Sonnet 5	$0.00002	$0.00119
Haiku 4.5	$0.00001	$0.00060

Measured 13d ago against content hash fc4915e26f8b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

investigate-sentry-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 13d 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.

plugin/commands/investigate-sentry-issue.md · 76 lines

How it starts

The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Investigate Sentry Issue

Investigate a Sentry issue to understand the error, gather context, and prepare for fixing or triaging.

Prerequisites

SENTRY_AUTH_TOKEN and SENTRY_ORG must be set. Verify with sentry-cli info.

Arguments

sentry-issue-url-or-id: A Sentry issue URL or just the issue ID (e.g., 123456)

Workflow

1. Parse the Input

If given a URL (https://sentry.io/organizations/{org}/issues/{issue_id}/), extract the issue ID.

2. Get Issue Overview

sentry-cli issues list --id <issue-id>

3. Get Detailed Info via REST API

Use https://sentry.io/api/0/organizations/${SENTRY_ORG}/issues/<issue-id>/ for metadata (first/last seen, event count, user impact, status).

4. Get Full Stacktrace

Use the recommended event endpoint: .../issues/<issue-id>/events/recommended/

Key jq paths for the response:

.entries[] | select(.type == "exception") — exception with stacktrace
.entries[] | select(.type == "exception") | .data.values[].stacktrace.frames — stack frames
.entries[] | select(.type == "breadcrumbs") — actions leading to the error
.tags — environment, browser, OS info
.context — custom context data

5. Analyze and Report

Identify the failing file and line number
Understand the error type and message
Review breadcrumbs for the sequence of events
Check tags for environment-specific issues

6. Take Action (if appropriate)

sentry-cli issues resolve <issue-id>    # Resolve
sentry-cli issues mute <issue-id>       # Mute
sentry-cli issues unresolve <issue-id>  # Unresolve

Search Query Syntax

Use these filters with sentry-cli issues list --query:

Filter	Example	Description
`is:`	`is:unresolved`	Issue status
`lastSeen:`	`lastSeen:-2d`	Seen within time range
`message:`	`message:undefined`	Match error message
`issue.category:`	`issue.category:error`	Error category

Tips

Always get the recommended event first — it's curated for debugging
Check breadcrumbs to understand user actions before the error
If investigating from a Slack alert, the issue URL is in the alert message

Read the full file on GitHub · 76 lines

Changes

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.

13d ago First seen · 76 lines · 10 tokens per session scan A fc4915e26f8b

Subscribe to this mod's changes

investigate-sentry-issue is a command published in the GitHub repository desplega-ai/agent-swarm (762 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 596 once invoked, about $0.0001 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.

Debugging agentic agentic-framework agentic-os ai-agents ai-memory-system harness-execution-layer

investigate-sentry-issue