fp-check

Verifies suspected security bugs and produces true positive or false positive verdicts with documented evidence.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/marumo333/atrox --skill fp-check-marumo333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fp-check
Source: https://github.com/marumo333/atrox/tree/main/.claude/skills/trailofbits/plugins/fp-check/skills/fp-check
Command: npx skills add https://github.com/marumo333/atrox --skill fp-check-marumo333

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security audits and static analysis tools generate many suspected bugs, but a large share are false positives. This Skill systematically verifies each suspected vulnerability through data flow tracing, mathematical bounds proofs, exploitability analysis, and devil's advocate review, so you only act on real, exploitable bugs. ## Core Features & Use Cases - Routed Verification Paths: Routes each bug to a linear standard checklist for straightforward claims or a full task-based deep verification workflow for complex, cross-component, or concurrency-related bugs. - Evidence-Based Verdicts: Applies six mandatory gate reviews (process, reachability, impact, PoC, math bounds, environment) and issues TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence. - Bug-Class Guidance: Provides class-specific verification requirements for memory corruption, logic bugs, race conditions, integer issues, crypto weaknesses, injection, information disclosure, DoS, and deserialization. - Use Case: After a security scanner flags 20 potential vulnerabilities in a C codebase, run this Skill to verify each finding, collapse obvious false positives during claim restatement, and receive a final summary of confirmed bugs with proof-of-concept sketches. ## Quick Start Ask the AI to verify whether a specific suspected vulnerability in your code is a true positive or a false positive.

Frequently Asked Questions about fp-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify if a security bug is a false positive?▼

Restate the exact vulnerability claim, trace data flow from source to sink, prove attacker control and mathematical bounds, then apply the six gate reviews. The Skill issues a FALSE POSITIVE verdict with the specific reason if any gate fails.

How to validate static analysis security findings?▼

Run each finding through claim restatement, then route it to standard verification for simple bugs or deep verification for complex ones. Every bug gets data flow analysis, exploitability proof, impact assessment, and a devil's advocate review before a verdict.

When should I use deep verification instead of standard verification?▼

Use deep verification for ambiguous claims, cross-component bug paths spanning 3+ modules, race conditions or TOCTOU triggers, logic bugs without a clear spec, or when standard verification reaches an escalation checkpoint with unresolved uncertainty.

Can memory corruption bugs exist in safe Rust or Go code?▼

Memory corruption in safe Rust, Go without unsafe.Pointer or cgo, or managed languages is almost always a false positive because the type system or runtime prevents it. Verify whether the code uses unsafe blocks or native calls before accepting the claim.

What are the limitations of automated false positive checking?▼

This Skill verifies specific suspected bugs and does not hunt for new vulnerabilities or perform general code review. It requires a concrete vulnerability claim with an alleged root cause and trigger to begin verification.