resolve

resolve is a command for Claude Code from ThibautBaissac/rails_ai_agents. It costs 17 tokens per session (441 once invoked), scanned A, original, MIT.

A command for changing the status of a Sentry issue after a fix is deployed. Sentry is an error-monitoring service that records application failures and their occurrences.

In plain words
What is it for?
Use it to resolve, ignore, or reopen a Sentry issue by its numeric ID.
Why use it?
It lets developers manage the issue lifecycle from the coding-agent workflow and confirm the issue before changing its status.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

Good fit Use it to resolve, ignore, or reopen a Sentry issue by its numeric ID.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/thibautbaissac/rails_ai_agents/resolve
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/ThibautBaissac/rails_ai_agents

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.

agentmods badge for resolve

README.md
[![agentmods](https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/resolve/github.svg)](https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/resolve)
Your own site
<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/resolve"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/resolve/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.

agentmods 80×15 button for resolve

Your own site · 80×15
<a href="https://agentmods.dev/commands/thibautbaissac/rails_ai_agents/resolve"><img src="https://agentmods.dev/badge/commands/thibautbaissac/rails_ai_agents/resolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 441 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00017 $0.00441
Opus 5 $0.00009 $0.00220
Sonnet 5 $0.00003 $0.00088
Haiku 4.5 $0.00002 $0.00044

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

Security

Grade A, and why

resolve 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 8d 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.

.claude/commands/sentry/resolve.md · 52 lines

What it actually says

Resolve: Update Sentry Issue Status

Update the status of a Sentry issue directly from Claude Code after verifying a fix.

Input

$ARGUMENTS — Sentry issue ID, optionally followed by a status.

Examples:

  • /sentry:resolve 12345 — resolve the issue
  • /sentry:resolve 12345 ignored — ignore the issue
  • /sentry:resolve 12345 unresolved — reopen the issue

Workflow

  1. Parse arguments: Extract the issue ID (first argument, numeric) and optional status (second argument, defaults to "resolved").

    • If no issue ID is provided, ask the developer for one.
    • Validate the status is one of: resolved, ignored, unresolved.
  2. Fetch current state: Call get_issue_detail with the issue ID to confirm it exists and show its current status.

    • Display: issue title, current status, error count, last seen date.
  3. Confirm action: Before making the change, ask the developer to confirm:

    Issue: {short_id} — {title}
    Current status: {status}
    Action: Change to "{new_status}"
    
    Proceed? (yes/no)
    
  4. Update status: Call the resolve_issue MCP tool with the issue ID and status.

  5. Report result:

    Updated {short_id} — {title}
    Status: {old_status} → {new_status}
    Sentry link: {permalink}
    

Notes

  • This command always asks for confirmation before making changes.
  • The resolve_issue tool requires project:write scope on the Sentry auth token.
  • For advanced options (resolve in next release, ignore for N minutes), call the resolve_issue tool directly with the appropriate parameters.
  • After merging a fix branch from /sentry:fix-error, use this command to close the loop in Sentry.
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.

  1. 8d ago First seen · 52 lines · 17 tokens per session scan A 1e9a6494ee6a

Subscribe to this mod's changes

resolve is a command published in the GitHub repository ThibautBaissac/rails_ai_agents (663 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 441 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-09-03.