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/ThibautBaissac/rails_ai_agentsWrote 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/thibautbaissac/rails_ai_agents/resolve)<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.
<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>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.00017 | $0.00441 |
| Opus 5.5 | $0.00007 | $0.00176 |
| Sonnet 5.5 | $0.00003 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
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 2mo 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.
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
-
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.
-
Fetch current state: Call
get_issue_detailwith the issue ID to confirm it exists and show its current status.- Display: issue title, current status, error count, last seen date.
-
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) -
Update status: Call the
resolve_issueMCP tool with the issue ID and status. -
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_issuetool requiresproject:writescope on the Sentry auth token. - For advanced options (resolve in next release, ignore for N minutes), call the
resolve_issuetool directly with the appropriate parameters. - After merging a fix branch from
/sentry:fix-error, use this command to close the loop in Sentry.
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.
- 2mo ago First seen · 52 lines · 17 tokens per session scan A 1e9a6494ee6a
resolve is a command published in the GitHub repository ThibautBaissac/rails_ai_agents (672 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 441 once invoked, about $0.0001 per session on Opus 5.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.
resolve compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| resolveThibautBaissac/rails_ai_agents | Command | 672 | 5mo ago | MIT | A | 17 | Claude Code |
| qa-changesOpenHands/extensions | Command | 176 | yesterday | MIT | A | 63 | Claude Code |
| react-nativegetsentry/toolkit | Command | 957 | yesterday | none | A | 0 | Claude Code |
| auditar-cascadingluanpdd/kit-mcp | Command | 5 | 4d ago | MIT | A | 54 | Claude Code |
| http-serviceMadAppGang/magus | Command | 14 | yesterday | MIT | A | 27 | Claude Code |
| doctordoncheli/don-cheli-sdd | Command | 59 | 2mo ago | Apache-2.0 | A | 76 | Claude Code |
| doctorfatihkan/badi | Command | 7 | 1mo ago | MIT | A | 0 | Claude Code |