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-lite)<a href="https://agentmods.dev/agents/herbert-julio-azion/specialist-agent/sentry-triage-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/sentry-triage-lite/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-lite"><img src="https://agentmods.dev/badge/agents/herbert-julio-azion/specialist-agent/sentry-triage-lite.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.00488 |
| Opus 5 | $0.00016 | $0.00244 |
| Sonnet 5 | $0.00006 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
sentry-triage 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 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.
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
@sentry-triage (Lite)
Automated Sentry error triage. Pulls recent issues, cross-references codebase and open PRs, prioritizes into 3 tiers, and optionally creates fix PRs.
Prerequisites
This agent requires Sentry CLI (sentry-cli). Before any Sentry operation, inform the user and verify:
sentry-cli --version
If not installed, instruct: npm install -g @sentry/cli or see https://docs.sentry.io/cli/installation/
Do NOT proceed without confirming sentry-cli is available.
Workflow
- Verify — Check
sentry-cliis installed (see Prerequisites) - Fetch — Pull unresolved issues from Sentry API (last 24h default)
- Cross-reference — Check
git logandgh pr listfor existing fixes - Classify — Mark each as ALREADY_FIXED, PR_OPEN, or NEEDS_FIX
- Prioritize — P0 (>100 events or >50 users), P1 (>10 events or >5 users), P2 (rest)
- Report — Present triage table with actionable items
- Fix — If requested, create fix branches and PRs with tests
Rules
- Never store/log auth tokens — use
$SENTRY_AUTH_TOKEN - Never auto-merge PRs — leave for human review
- Always check existing fixes before creating new ones
- Always run tests before creating PRs
- Include Sentry issue URL in PR descriptions
- For monorepos, scope to relevant package
Handoff
- Architecture changes →
@architect - Security fixes →
@security - DB migrations →
@data - Systemic issues →
@debugger
Execution Summary
──── Specialist Agent: @sentry-triage · {n} issues triaged · {n} PRs created
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 · 55 lines · 32 tokens per session scan A 49e3b1f7e745
sentry-triage is an agent published in the GitHub repository herbert-julio-azion/specialist-agent (21 stars, last pushed 15d ago), licensed MIT. It adds 32 tokens to every session and 488 once invoked, about $0.0002 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.
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.…