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-perf/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-perf)<a href="https://agentmods.dev/skills/brizzai/fleet/debug-perf"><img src="https://agentmods.dev/badge/skills/brizzai/fleet/debug-perf/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-perf"><img src="https://agentmods.dev/badge/skills/brizzai/fleet/debug-perf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Rogue Agent · line 94 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.00111 | $0.02352 |
| Opus 5.5 | $0.00044 | $0.00941 |
| Sonnet 5.5 | $0.00022 | $0.00470 |
| Haiku 4.5 | $0.00011 | $0.00235 |
Grade A, and why
debug-perf 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Performance / UI Stalls
Diagnose why the fleet TUI froze, stuttered, or felt laggy by reading the artifacts the perfwatch package writes when FLEET_DEBUG=1 is set. Read-only — report findings and recommend fixes, never edit code.
What perfwatch records
When FLEET_DEBUG=1, internal/perfwatch instruments every Update() call and continuously samples runtime state:
- Stall dumps —
~/.config/fleet/stalls/<ts>_update_stall_<msgType>_<ms>ms.txtwritten automatically whenUpdate()runs longer than 500ms. Re-dumps every 1.5s while still stuck. Contains: in-flight message, recent message ring buffer (last 32 with durations), full goroutine stacks (debug=2), block profile, mutex profile, GC stats. - Heartbeat — every 5s in
~/.config/fleet/debug.log: goroutine count, process CPU%, heap KB, total/slow update counts, max update duration. Keeps logging during attach (when the Bubble Tea loop is suspended) so background-worker CPU usage is visible even when the TUI itself isn't running. - Slow Update warnings — any
Update()≥100ms gets aperfwatch: slow Update msg=… duration_ms=…WARN line in debug.log even if it didn't trigger a stall dump. - SIGUSR1 —
kill -USR1 $(pgrep -f 'fleet$')forces a snapshot on demand. Filename ends in_manual_sigusr1.
Step 0: Verify perfwatch is enabled
If the user hasn't set FLEET_DEBUG, no dumps exist and you can't help. Check:
grep "perfwatch: enabled" ~/.config/fleet/debug.log | tail -1
If empty, instruct the user:
Re-launch with: FLEET_DEBUG=1 ./build/fleet
Reproduce the freeze, then run /debug-perf again.
If the user reports laggy attach but no TUI stall, also tell them: while attach feels laggy, run kill -USR1 $(pgrep -f 'fleet$') from another terminal to force a snapshot of background goroutines. Stalls during attach won't trigger the watchdog (Bubble Tea loop is suspended), so manual snapshots are the only signal.
Step 1: Find the relevant dump
ls -lt ~/.config/fleet/stalls/ | head -20
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 · 162 lines · 111 tokens per session scan A 1543d4800df9
debug-perf is a skill published in the GitHub repository brizzai/fleet (59 stars, last pushed 9d ago), licensed Apache-2.0. It adds 111 tokens to every session and 2,352 once invoked, about $0.0004 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
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.