FP Check takes a specific suspected vulnerability and decides whether it is real. It restates the claim, traces the data flow from source to sink, applies class-specific checks, and ends each bug with a verdict and its evidence.
Simple claims follow a linear checklist. Complex ones (cross-component paths, races, ambiguous logic bugs) go through a task-based deep verification with six mandatory gate reviews. It is for verifying findings, not for hunting new ones.
What You Get
- A TRUE POSITIVE or FALSE POSITIVE verdict for every suspected bug
- Documented evidence: data flow traces, attacker control analysis and devil’s advocate reviews
- A final summary with counts and a short reason for each rejection
- Class-specific checks for memory corruption, logic bugs, races, integer issues, crypto, injection, disclosure, denial of service and deserialization
Common Use Cases
- Checking whether a static analyzer finding is exploitable
- Validating a bug report from a bounty submission
- Triaging a batch of scanner results before they reach developers
- Confirming a suspected race condition or logic flaw
What Makes It Unique
It is built to counter the bias of language models toward seeing bugs and overrating severity. A table of rationalizations to reject blocks shortcuts such as reporting code that merely looks unsafe, and each bug must pass all mandatory gate reviews. It also keeps discovery out of scope, so it verifies claims and does not search for new ones.
Under The Hood
The skill is prose with reference files for standard verification, deep verification, gate reviews, bug classes, false positive patterns and evidence templates. The agent reads and searches the code under review, may run shell commands to test a claim, can write evidence files, and in deep mode dispatches the plugin’s analysis agents and tracks phases as tasks. It asks you questions when a claim is unclear. It makes no web requests of its own.