fp check

Other Community

Skill notes

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

Step 0: Understand the Claim and Context

Before any analysis, restate the bug in your own words. If you cannot do this clearly, ask the user for clarification. Half of false positives collapse at this step — the claim doesn't make coherent sense when restated precisely. Document: What is the exact vulnerability claim? (e.g., "heap buffer overflow in parse_header() when content_length exceeds 4096") What is the alleged root cause? (e.g., "missing bounds check before memcpy at line 142")

Route: Standard vs Deep Verification

After Step 0, choose a verification path.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 0: Understand the Claim and Context

Before any analysis, restate the bug in your own words. If you cannot do this clearly, ask the user for clarification. Half of false positives collapse at this step — the claim doesn't make coherent sense when restated precisely. Document: What is the exact vulnerability claim? (e.g., "heap buffer overflow in `parse_header()` when `content_length` exceeds 4096") What is the alleged root cause? (e.g., "missing bounds check before `memcpy` at line 142")

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.