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.
npx skills add DVNghiem/FlowDeck --skill debug-flowgit clone --depth 1 https://github.com/DVNghiem/FlowDeckWrote 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/dvnghiem/flowdeck/debug-flow)<a href="https://agentmods.dev/skills/dvnghiem/flowdeck/debug-flow"><img src="https://agentmods.dev/badge/skills/dvnghiem/flowdeck/debug-flow/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/dvnghiem/flowdeck/debug-flow"><img src="https://agentmods.dev/badge/skills/dvnghiem/flowdeck/debug-flow.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 MCP Rug Pull · line 50 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00034 | $0.00703 |
| Opus 5.5 | $0.00014 | $0.00281 |
| Sonnet 5.5 | $0.00007 | $0.00141 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
debug-flow 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 1mo 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Flow Skill
Finds root causes through systematic investigation. Does not guess. Does not fix symptoms.
When to Activate
Activate when:
- A bug has been reported
- Code is producing unexpected output
- Tests are failing intermittently
- An error is occurring in production
Core Principles
- Read stack traces completely — never skip to the middle
- Fix root causes, not symptoms
- Check recent changes first —
git log --oneline -20 - Reproduce before fixing — if you can't reproduce it, you don't understand it
Workflow
- Reproduce — confirm you can make the bug happen reliably
- Read the full stack trace — start from the top (error), trace to the origin
- Check recent changes —
git log --oneline -20to find what changed - Trace execution backward — what called the failing function? What state did it receive?
- Identify root cause — the earliest point where invariants are violated
- Write a failing test — one test that fails with the bug present
- Fix — change the minimum code to make the test pass
- Verify — run the full test suite
Common Root Causes
| Symptom | Likely Cause | Investigation |
|---|---|---|
Cannot read property of undefined |
Missing null check upstream | Trace where undefined enters |
| Wrong calculation result | Type coercion ("5" + 3 = "53") |
Check input types |
| Race condition / intermittent | Missing await |
Find async functions called without await |
| Auth bypass | Missing middleware | Check route definition vs working routes |
| Infinite loop | Wrong termination condition | Log loop counter, check exit logic |
| Memory leak | Event listener not cleaned up | Check useEffect returns, removeListener calls |
| Promise rejection unhandled | Missing .catch() or try/catch |
Check all async call sites |
| Type error at runtime | as any hiding real type |
Find where the cast was added |
| Stale data in UI | Cache not invalidated | Check cache keys and invalidation logic |
| Import error | Circular dependency or missing export | npx madge --circular src/ |
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.
- 1mo ago First seen · 76 lines · 34 tokens per session scan A 4134d4458d43
debug-flow is a skill published in the GitHub repository DVNghiem/FlowDeck (36 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 703 once invoked, about $0.0001 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
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
nw-bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
polya-fix
Phase 5 of the Pólya Heuristic Coder: First-Principles Bug Remediation, Seam Tracing, Bisection Search (O(log n)), Failing Reproduction Tests, and Incubation Circuit-Breaker Gate (docs/bug-reports/{slug}-bugfix.md).
hatch3r-bug-fix
Step-by-step bug fix workflow. Diagnose root cause, implement minimal fix, write regression test. Use when fixing bugs, working on bug report issues, or when the user mentions a bug.
debugging
A structured method for finding and fixing software bugs. It starts by writing a test that reproduces the failure, then investigates its underlying cause before making a small fix.
hk-rca
Interactive Root Cause Analysis enforcer. Guides you through the 7-step RCA protocol: Reproduce, Locate, Hypothesis, Failing Test, Fix, Verify Live, Document. Use when debugging a bug, investigating a failure, or when something unexpected happened. This skill gates each step — it won't let you skip to a fix without…