Fallow is a command-line static-analysis tool that builds a dependency graph of TypeScript and JavaScript code to identify unused code, duplication, circular dependencies, complexity hotspots, boundary violations, and styling drift. It is for developers reviewing codebases and verifying changes, with catalogue entries that add agent, editor, and workflow integrations.
Borrowing it
Nothing to install: this file belongs to fallow-rs/fallow. 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/fallow-rs/fallow/main/.agents/skills/debug-false-positive/SKILL.mdgit clone --depth 1 https://github.com/fallow-rs/fallowWrote 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/fallow-rs/fallow/debug-false-positive)<a href="https://agentmods.dev/skills/fallow-rs/fallow/debug-false-positive"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow/debug-false-positive/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/fallow-rs/fallow/debug-false-positive"><img src="https://agentmods.dev/badge/skills/fallow-rs/fallow/debug-false-positive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00298 |
| Opus 5.5 | $0.00014 | $0.00119 |
| Sonnet 5.5 | $0.00007 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
debug-false-positive 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 23d 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.
What it actually says
Debug a false result
- Reproduce on current
mainwith--format json --quiet. Save one command that shows the wrong result. Change no code before this command exists. After a restart or an update, clear the.fallow/cache first. - Reduce to a minimal fixture without losing the behavior.
- Write 3 to 5 ranked hypotheses. Each one predicts a result that one probe can disprove. Test one hypothesis per probe.
- Trace the finding through extract, resolve, graph, reachability, analysis, suppression, filters, and report assembly.
- Fix the earliest incorrect layer. Fix the pattern, not the instance (see
test evidence in
docs/development/quality-gates.md). After 3 failed fixes, stop and write down the premise that they share. Question that premise before a fourth fix. - Add a regression test that fails without the fix.
- Run the fixed binary on a real consumer project with a cleared
.fallow/cache and compare old versus new output. - Run
reviewwith the affected surface reviewers.
Do not tune expected output around one fixture when the semantic model requires a broader correction.
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.
- 23d ago Changed · +7 lines 93fed1a0d6f9
- 1mo ago First seen · 20 lines · 34 tokens per session scan A 898ca094c7aa
debug-false-positive is a skill published in the GitHub repository fallow-rs/fallow (5,139 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 298 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
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
argot-refresh
Refresh Argot's committed fit snapshot safely — first diagnose why maintenance is recommended, re-audit corpus scope and structural path changes, review stale mutes and policy entries with the user, then fit locally, verify, and prepare the reviewed .argot/ update. Use when argot status, argot check, MCP, or CI…
poly-tiers-and-scope
Five mechanisms decide what actually inspects a file (crates/poly-core/src/registry.rs).
poly-mcp
The poly MCP server — the eleven tools and which are read-only vs mutating, the paths/exclude/config/format params, async Tasks for the whole-project phase, and the isError contract.
ph-debug
(PH) Use for a reproducible failure or unexpected behavior; reproduce, isolate, and verify the cause.
ph-lsp-setup
(PH) Use only when the user explicitly requests language-server setup or diagnostics.