Borrowing it
Nothing to install: this file belongs to brizzai/fleet. 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/brizzai/fleet/master/.claude/skills/debug-status/SKILL.mdgit clone --depth 1 https://github.com/brizzai/fleetWrote 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/brizzai/fleet/debug-status)<a href="https://agentmods.dev/skills/brizzai/fleet/debug-status"><img src="https://agentmods.dev/badge/skills/brizzai/fleet/debug-status/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/brizzai/fleet/debug-status"><img src="https://agentmods.dev/badge/skills/brizzai/fleet/debug-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Agent Snooping · line 125 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 199 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- high Agent Snooping · line 199 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
- medium Rogue Agent · line 120 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00046 | $0.04049 |
| Opus 5.5 | $0.00018 | $0.01620 |
| Sonnet 5.5 | $0.00009 | $0.00810 |
| Haiku 4.5 | $0.00005 | $0.00405 |
Grade B, and why
debug-status scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
grep -l "\"$CS\"" ~/.claude/sessions/*.json 2>/dev/null | while read -r f; do How it starts
The opening of the file, as written. The whole thing — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Session Status
Diagnose why a fleet session shows the wrong status. Read-only — report findings and recommend fixes, never edit code.
For architecture details, see reference.md.
Approach
Status flows through a pipeline. Your job is to trace the pipeline and find where it breaks:
Claude Code → hook event → hook-handler binary → status file → fsnotify → UpdateStatus() → TUI
↓
pane capture + conversation-log (JSONL) + Claude session status file — fallback/supplement
At each stage, ask: what does this stage think the status is, and is it correct?
The conversation log (~/.claude/projects/*/<claude_session_id>.jsonl) is a fourth, often-decisive signal: it is appended on real conversation events (tool calls, results, thinking), so unlike the pane it is immune to repaint/spinner/queued-message quirks. Its key use: if the log's last entry is newer than a waiting hook's timestamp, the user already acted and the agent resumed — the session is running even though the hook still says waiting. (It can only confirm running, not waiting: a genuine unanswered prompt and a long-running tool both leave the log static — see Step 2.)
The Claude session status file (~/.claude/sessions/<pid>.json, one per live claude process) is a fifth signal — the only one carrying Claude Code's own status flag (busy / idle / shell) rather than something fleet infers. It's keyed by pid but records sessionId, so you match it to a fleet session by the hook's session_id. Best use: a clean Running-vs-Idle corroborator when the pane is ambiguous. Three sharp limits: (1) trust the value, not statusUpdatedAt — it's event-driven, not a heartbeat, so a busy turn can carry a minutes-old timestamp; gate on whether the pid is alive instead. (2) No waiting value — a permission prompt reads idle/busy here, so it can't source Waiting. (3) Blind to /compact — compaction isn't counted as busy, so it stays idle right through a multi-minute compaction (see Step 2's compaction note). fleet does not consult this file for status detection yet, but the D snapshot does freeze it (claude_session_status.json + a claude_status block in snapshot.json).
What ships with it
1 file 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 · 275 lines · 46 tokens per session scan B a7a6f42108f5
debug-status is a skill published in the GitHub repository brizzai/fleet (59 stars, last pushed 9d ago), licensed Apache-2.0. It adds 46 tokens to every session and 4,049 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.