fp-check

Classify security scanner findings as false positives or real vulnerabilities.

5|2|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/NOMARJ/sigil --skill fp-check-nomarj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fp-check
Source: https://github.com/NOMARJ/sigil/tree/main/packs/security/skills/owasp-security/fp-check
Command: npx skills add https://github.com/NOMARJ/sigil --skill fp-check-nomarj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a mandatory false-positive gate for security scanner findings so teams can separate noise from actionable vulnerabilities and avoid alert fatigue.

Core Features & Use Cases

  • Hard exclusion rules: Automatically classify common low-signal categories (DOS, test files, docs, safe-language memory issues, prompt injection, etc.) as auto-excluded false positives.
  • Confidence gating & triage: Assign 1-10 confidence scores with an explicit threshold that determines whether findings require manual triage or can be logged as FP.
  • Reproduction, classification, and allowlist management: Step-by-step triage protocol that mandates reproduction attempts, TP/FP/AR classification, documented justifications, and allowlist entries with review dates.

Quick Start

Use fp-check to triage the latest security scanner findings and produce a FP-CHECK TRIAGE summary.

Frequently Asked Questions about fp-check

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

FAQPage Schema
How do I filter false positives from security scanner findings?

To filter false positives from security scanner findings, apply hard exclusion rules for low-signal categories like DOS and test files, then use confidence scoring with defined thresholds to gate noise from actionable vulnerabilities.

What is the best way to triage automated scan outputs across repositories?

The best way to triage automated scan outputs across repositories is to enforce a step-by-step protocol mandating reproduction attempts, TP/FP/AR classification, documented justifications, and allowlist entries with scheduled review dates.

How do confidence scores work in vulnerability triage?

Confidence scores in vulnerability triage work by assigning a 1-10 rating to each finding, using an explicit threshold to determine whether scanner results require manual review or can be automatically logged as false positives.

Can I automatically exclude prompt injection findings from CI scan results?

Yes, you can automatically exclude prompt injection findings from CI scan results by applying hard exclusion rules that classify common low-signal categories, including prompt injection, docs, and safe-language memory issues, as auto-excluded false positives.

Why should I use an allowlist when triaging scanner vulnerabilities?

You should use an allowlist when triaging scanner vulnerabilities to prevent reflagging of documented noise, ensuring that previously reviewed false positives include review dates and justifications to maintain signal quality over time.