fp-check

Verify suspected security vulnerabilities and classify them as true or false positives.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/rauly-1408/order-saas --skill fp-check-rauly-1408
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fp-check
Source: https://github.com/rauly-1408/order-saas/tree/main/.claude/skills/fp-check
Command: npx skills add https://github.com/rauly-1408/order-saas --skill fp-check-rauly-1408

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security reviewers determine whether suspected vulnerabilities are real issues or false positives by enforcing a structured verification process with evidence-based conclusions.

Core Features & Use Cases

  • Vulnerability Verification Workflow: Guides analysts through claim restatement, threat modeling, data flow tracing, and evidence collection before reaching a verdict.
  • False Positive Reduction: Uses standard and deep verification paths to avoid reporting unproven security issues.
  • Use Case: Review a reported SQL injection, memory corruption, or logic flaw and produce a TRUE POSITIVE or FALSE POSITIVE assessment with supporting reasoning.

Quick Start

Use the fp-check skill to verify whether the reported security vulnerability in the provided code is exploitable and document the final verdict.

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 reported security vulnerability is a true positive or false positive?

Vulnerability verification involves restating the claim, applying threat modeling, tracing data flows, and collecting evidence to determine whether a suspected security issue is exploitable and classify it as a true positive or false positive.

What is the best way to reduce false positives during code review?

Reducing false positives during code review requires enforcing a structured verification process using standard and deep verification paths, ensuring analysts document evidence-based conclusions before reporting unproven security vulnerabilities.

How does data flow tracing work for vulnerability validation?

Data flow tracing for vulnerability validation works by tracking how untrusted inputs move through application logic, allowing security reviewers to confirm exploitability and produce a documented verdict for suspected flaws like SQL injection or memory corruption.

Can I use this to triage memory corruption and logic flaws?

Yes, you can use this process to triage memory corruption and logic flaws. It guides analysts through threat modeling and evidence collection to assess whether these specific suspected vulnerabilities are exploitable.

Do I need threat modeling to check exploitability of a suspected bug?

Yes, threat modeling is required to check exploitability. It provides the structured analysis workflow needed to evaluate the attack surface and verify whether a suspected bug represents a genuine security threat.

Why should I use structured analysis workflows for security findings?

Structured analysis workflows prevent reporting unproven security issues by ensuring reviewers collect concrete evidence and trace data flows before reaching a final true positive or false positive conclusion.