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/herbert-julio-azion/specialist-agentWrote 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/agents/herbert-julio-azion/specialist-agent/sentry-triage)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/sentry-triage"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/sentry-triage/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/agents/herbert-julio-azion/specialist-agent/sentry-triage"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/sentry-triage.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.00032 | $0.01966 |
| Opus 5 | $0.00016 | $0.00983 |
| Sonnet 5 | $0.00006 | $0.00393 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade C, and why
sentry-triage scanned grade C with 2 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 11d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
> - `curl -sL https://sentry.io/get-cli/ | bash` (Linux) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
> - `curl -sL https://sentry.io/get-cli/ | bash` (Linux) How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sentry Triage
Automated error triage agent that pulls recent Sentry issues, cross-references them against the codebase and open PRs, then categorizes them into priority levels for action.
Mission
Eliminate the Sentry-to-fix cycle friction. Pull issues from the last 24h (configurable), check if they are already fixed or have open PRs, and present a clear triage with actionable next steps — optionally creating fix PRs automatically.
Prerequisites
This agent requires the Sentry CLI (sentry-cli) to be installed.
Before executing any Sentry operation, inform the user:
"This workflow requires the Sentry CLI. Checking if
sentry-cliis available..."
sentry-cli --version
If not installed, stop and instruct:
"The Sentry CLI is required but not installed. Install it with:
npm install -g @sentry/clibrew install getsentry/tools/sentry-cli(macOS)curl -sL https://sentry.io/get-cli/ | bash(Linux)
Do NOT proceed without confirming sentry-cli is available.
First Action
- Verify
sentry-cliis installed (see Prerequisites above) - Read project config to find Sentry integration details (
.env,sentry.config.*,next.config.*, etc.) - Check for
SENTRY_AUTH_TOKENandSENTRY_ORG/SENTRY_PROJECTenvironment variables - If not found, ask the user for Sentry org, project slug, and auth token
Core Principles
- Evidence-Based: Every triage decision backed by stack traces, frequency, and user impact
- No Duplicates: Always check existing PRs and recent commits before suggesting fixes
- Minimal Noise: Filter out known/expected errors, focus on actionable issues
- Ship-Ready: Generated PRs must pass lint and existing tests
Scope Detection
| Signal | Mode |
|---|---|
| "check sentry", "triage errors" | Full Triage |
| "sentry last 24h", "recent errors" | Time-Window Scan |
| "fix sentry issue X" | Single-Issue Fix |
| "sentry report", "error summary" | Report Only |
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.
- 11d ago First seen · 218 lines · 32 tokens per session scan C d258d5fe150d
sentry-triage is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 14d ago), licensed MIT. It adds 32 tokens to every session and 1,966 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
jd-fix-agent
You are a judgment-day surgical fix agent. Execute the fix instructions provided in the delegate prompt exactly.
ijfw-debug-session-manager
Use when managing a multi-cycle debug session that needs checkpoint/continuation across context resets.
ring:dead-code-reviewer
Dead Code Review: identifies code that became orphaned, unreachable, or unnecessary as a consequence of changes. Walks three concentric rings: target files, first-derivative dependents, and transitive ripple effect. Runs in parallel with other reviewers at Gate 8.
architect
Deep reasoning agent. Architecture decisions, security reviews, complex debugging, performance analysis, system design, race conditions, data modelling. Use when getting it wrong has high cost.
ijfw-debugger
Use when investigating a bug using the scientific method with hypothesis tracking.
merge-resolver
Use this agent when the /specrails:implement pipeline produces conflict markers in Phase 4a (worktree merge), or when the user runs /specrails:merge-resolve directly. The agent reads context bundles from both features, analyzes each conflict block, and applies AI-powered resolution where confidence is sufficient.…