Agent skill · Security

fp-check

Systematically verifies suspected security bugs to eliminate false positives. Produces TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence for each bug.

Wayner Barrios443★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add waybarrios/opencode-power-pack --skill fp-check --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 7
SKILL.md size: 6 KB
Bundled scripts: none
Path: skills/fp-check/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 443
Language: JavaScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# False Positive Check ## When to Use - "Is this bug real?" or "is this a true positive?" - "Is this a false positive?" or "verify this finding" - "Check if this vulnerability is exploitable" - Any request to verify or validate a specific suspected bug ## When NOT to Use - Finding or hunting for bugs ("find bugs", "security analysis", "audit code") - General code review for style, performance, or maintainability - Feature development, refactoring, or non-security tasks - When the user explicitly asks for a quick scan without verification ## Rationalizations to Reject If you catch yourself thinking any of these, STOP. | Rationalization | Why It's Wrong | Required Action | |---|---|---| | "Rapid analysis of remaining bugs" | Every bug gets full verification | Return to task list, verify next bug through all phases | | "This pattern looks dangerous, so it's a vulnerability" | Pattern recognition is not analysis | Complete data flow tracing before any conclusion | | "Skipping full verification for efficiency" | No partial analysis allowed | Execute all steps per the chosen verification path | | "The code looks unsafe, reporting without tracing data flow" | Unsafe-looking code may have

What's inside
Steps it walks through
  1. When to Use
  2. When NOT to Use
  3. Rationalizations to Reject
  4. Step 0: Understand the Claim and Context
  5. Route: Standard vs Deep Verification
  6. Standard Verification
  7. Deep Verification
  8. Default
  9. Batch Triage
  10. Final Summary
  11. References
Ships with 6 files
  • references/bug-class-verification.md
  • references/deep-verification.md
  • references/evidence-templates.md
  • references/false-positive-patterns.md
  • references/gate-reviews.md
  • references/standard-verification.md
More from opencode-power-pack
All skills →
About this skill
What does the fp-check skill do?

Systematically verifies suspected security bugs to eliminate false positives. Produces TRUE POSITIVE or FALSE POSITIVE verdicts with documented evidence for each bug.

How do I install it?

Run `npx skills add waybarrios/opencode-power-pack --skill fp-check --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From waybarrios/opencode-power-pack, a repository with 443 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going