TitanX: Skill for Claude Code

.claude/skills/fix-sentry/SKILL.md

fix-sentry is a skill for Claude Code from CES-Ltd/TitanX. It costs 60 tokens per session (5,079 once invoked), scanned A, original, Apache-2.0.

An automated workflow for investigating frequent errors recorded in Sentry, a service that tracks software failures, and preparing code fixes.

In plain words
What is it for?
It is for fetching high-frequency Sentry issues, analyzing them, fixing code, creating GitHub issues, and submitting pull requests.
Why use it?
It reduces the manual work of finding recurring errors, examining their stack traces, and turning fixes into GitHub issues and pull requests.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths.

This is CES-Ltd/TitanX's own configuration. It tells Claude Code how to work on TitanX itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything TitanX configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/check-i18n.js.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/CES-Ltd/TitanX/main/.claude/skills/fix-sentry/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/CES-Ltd/TitanX

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 fix-sentry

README.md
[![agentmods](https://agentmods.dev/badge/skills/ces-ltd/titanx/fix-sentry/github.svg)](https://agentmods.dev/skills/ces-ltd/titanx/fix-sentry)
Your own site
<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.

agentmods 80×15 button for fix-sentry

Your own site · 80×15
<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>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,079 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.00060 $0.05079
Opus 5.5 $0.00024 $0.02032
Sonnet 5.5 $0.00012 $0.01016
Haiku 4.5 $0.00006 $0.00508

Measured 2mo ago against content hash 55d5ed33bdd7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/skills/fix-sentry/SKILL.md · 532 lines

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 limit parameter), 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 status shows 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:

  1. Read the file (if it doesn't exist, start with an empty skip list)
  2. Remove all entries where expires < current time (expired entries get re-analyzed)
  3. Keep the remaining entries as the active skip list

During Phase 1.2 (Fetch Issues):

Read the full file on GitHub · 532 lines

Files

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.

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. 2mo ago First seen · 532 lines · 60 tokens per session scan A 55d5ed33bdd7

Subscribe to this mod's changes

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.

Related

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.

runxhq/runx · 35 tokens

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.

runxhq/runx · 45 tokens

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…

FerroxLabs/wayland · 101 tokens

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…

comisai/comis · 89 tokens

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.

blueberrycongee/termcanvas · 53 tokens

feedback

Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.

Hmbown/Codewhale · 0 tokens