Borrowing it
Nothing to install: this file belongs to CES-Ltd/TitanX. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CES-Ltd/TitanX/main/.claude/skills/fix-sentry/SKILL.mdgit clone --depth 1 https://github.com/CES-Ltd/TitanXWrote 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/skills/ces-ltd/titanx/fix-sentry)<a href="https://agentmods.dev/skills/ces-ltd/titanx/fix-sentry"><img src="https://agentmods.dev/badge/skills/ces-ltd/titanx/fix-sentry/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/skills/ces-ltd/titanx/fix-sentry"><img src="https://agentmods.dev/badge/skills/ces-ltd/titanx/fix-sentry.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.00060 | $0.05079 |
| Opus 5.5 | $0.00024 | $0.02032 |
| Sonnet 5.5 | $0.00012 | $0.01016 |
| Haiku 4.5 | $0.00006 | $0.00508 |
Grade A, and why
fix-sentry 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.
How it starts
The opening of the file, as written. The whole thing — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Sentry Skill
Automated workflow: Sentry issues → analyze → fix → GitHub Issue → PR.
Announce at start: "I'm using fix-sentry skill to find and fix high-frequency Sentry issues."
Operating Modes
Batch Mode (default)
Invocation: /fix-sentry or /fix-sentry threshold=50
- Uses the specified threshold (default 100) to fetch issues
- Runs full Phase 1 → Phase 2 → Phase 3
- Fixes all qualifying issues
Daemon Mode
Invocation: /fix-sentry limit=1 (from daemon script)
- Phase 1 uses adaptive threshold descent: starts at 100, lowers progressively until a fixable issue is found
- Fixes only 1 issue (controlled by
limitparameter), then exits - If no fixable issue exists at any threshold → outputs
[NO_FIXABLE_ISSUES]and exits
Prerequisites
- Sentry MCP must be configured (global or project scope) with
mcp__sentry__*tools available - gh CLI must be authenticated
- Working directory must be clean (
git statusshows no uncommitted changes)
Workflow
Phase 1: Collect & Filter Issues
Step 1.1: Verify Environment
git status --porcelain # must be clean
git branch --show-current
If working directory is dirty, STOP and ask user to commit or stash first.
Step 1.1b: Load Skip List (Daemon Mode Only)
In daemon mode (limit > 0), load the skip list to avoid re-analyzing issues that were already
triaged in previous sessions. The skip list is stored at:
~/.aionui-fix-sentry/skip-list.json
Format:
{
"ELECTRON-6X": { "reason": "already_fixed", "expires": "2026-03-28T03:00:00Z", "summary": "PR #1758 merged" },
"ELECTRON-A7": { "reason": "system_level", "expires": "2026-04-03T03:00:00Z", "summary": "EPIPE in net.Socket" }
}
On load:
- Read the file (if it doesn't exist, start with an empty skip list)
- Remove all entries where
expires< current time (expired entries get re-analyzed) - Keep the remaining entries as the active skip list
During Phase 1.2 (Fetch Issues):
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 532 lines · 60 tokens per session scan A 55d5ed33bdd7
fix-sentry is a skill published in the GitHub repository CES-Ltd/TitanX (49 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 5,079 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
diagnose-skill-run
Diagnose a failed or suspicious Runx skill execution from receipts and harness evidence, then propose the smallest bounded improvement without replaying the failed operation.
postmortem-draft
Turn resolved-incident fragments into a traceable postmortem that separates fragment-cited facts from hypotheses, blocks publication while unknowns remain, and keeps the comms send behind a human gate.
business-ops-runbook-generator
Build an operational runbook with rollback paths for a recurring task or incident: capture the brief, infer failure modes, draft the runbook steps and checks, then define a rollback path for each failure mode. Use when the user wants a step-by-step runbook that an operator can follow under pressure, including what to…
log-troubleshooting
Investigate and troubleshoot daemon logs at /.comis/logs/. Covers NDJSON log format, Pino level codes, field dictionary, and staged analysis strategies for efficient troubleshooting of large log files. Use this skill whenever the user asks about logs, errors, warnings, daemon issues, slow operations, debugging daemon…
investigate
Systematic debugging skill. Use when encountering a bug, test failure, unexpected behavior, or when asked to "investigate", "debug", "diagnose", or "figure out why". Enforces root-cause-first discipline with structured hypothesis tracking.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.