[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NTTBS8RCQ7P1593W3Z1R8B":3,"skill-same:01M6NTTBS8RCQ7P1593W3Z1R8B":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":14,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M6NTTBS8RCQ7P1593W3Z1R8B","fp-check",null,"Systematic false positive verification for security findings. Provides structured methodology to confirm or dismiss scanner results, manual audit findings, and automated alerts. Adapted from Trail of Bits. Use when triaging security scan results or verifying audit findings.","rubicanjr\u002FFinCognis","rubicanjr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F234912519?v=4","01M6NT156NND8J474G34SB3923","Rubi","01M6NT15B70RWXE1N3YV0BZY8A",0,"MIT","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Ffp-check\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36],"fp check","check","scan","for","trail","manual","false","systematic","structured","alerts","security","scanner","use","results","methodology","audit","security scan","verification","2026-11-10 10:12:30",false,"---\nname: fp-check\ndescription: Systematic false positive verification for security findings. Provides structured methodology to confirm or dismiss scanner results, manual audit findings, and automated alerts. Adapted from Trail of Bits. Use when triaging security scan results or verifying audit findings.\n---\n\n# False Positive Verification\n\nNot every finding is real. But dismissing a real finding as \"false positive\" is worse than investigating a false one. This skill provides a systematic approach to verify findings without bias.\n\n## Verification Process\n\n### Step 1: Reproduce the Claim\n\nBefore dismissing anything, attempt to confirm:\n\n```\nFINDING: SQL injection in \u002Fapi\u002Fusers\nCLAIM: User input reaches database query unsanitized\n\nVERIFICATION:\n1. Read the actual code at the reported location\n2. Trace the data flow from input to sink\n3. Check for sanitization\u002Fvalidation between input and sink\n4. Check for framework-level protections (ORM, parameterized queries)\n5. Attempt to construct an exploit payload\n```\n\n### Step 2: Evidence-Based Triage\n\n| Verdict | Criteria | Evidence Required |\n|---------|----------|-------------------|\n| TRUE POSITIVE | Vulnerability exists and is exploitable | Code path + exploit scenario |\n| TRUE POSITIVE (mitigated) | Vulnerability exists but other controls prevent exploitation | Code path + mitigation proof |\n| FALSE POSITIVE (provable) | Finding is wrong due to tool limitation | Specific reason why tool was wrong |\n| FALSE POSITIVE (contextual) | Code is technically flagged but context makes it safe | Context documentation |\n| NEEDS INVESTIGATION | Cannot determine without more analysis | What additional info is needed |\n\n### Step 3: Document the Decision\n\n```\nFINDING: [scanner\u002Fauditor finding description]\nSOURCE: [which tool\u002Fperson reported it]\nLOCATION: file.ts:42\n\nVERDICT: [TRUE POSITIVE | FALSE POSITIVE | NEEDS INVESTIGATION]\n\nEVIDENCE:\n  - [What you checked]\n  - [What you found]\n  - [Why you reached this conclusion]\n\nREASONING:\n  [Detailed explanation of why this is\u002Fisn't a real finding]\n\nCONFIDENCE: [HIGH | MEDIUM | LOW]\n  [If LOW, explain what would increase confidence]\n```\n\n## Common False Positive Patterns\n\n### 1. Scanner Doesn't Understand Context\n\n```\nScanner says: \"Hardcoded password detected\"\nActual code: const DEFAULT_LABEL = \"password\"\nVerdict: FALSE POSITIVE -- it's a UI label, not a credential\nEvidence: Variable is used only in form field label rendering\n```\n\n### 2. Framework Protection Not Recognized\n\n```\nScanner says: \"SQL injection in query\"\nActual code: db.query(\"SELECT * FROM users WHERE id = $1\", [userId])\nVerdict: FALSE POSITIVE -- parameterized query prevents injection\nEvidence: $1 is a parameter placeholder, userId is bound safely\n```\n\n### 3. Dead Code \u002F Unreachable Path\n\n```\nScanner says: \"XSS in renderUserInput()\"\nActual code: renderUserInput() exists but is never called\nVerdict: FALSE POSITIVE -- function is dead code\nEvidence: grep shows no callers; function should be removed anyway\nWARNING: Verify it's truly unreachable, not just unused currently\n```\n\n### 4. Test Code Flagged\n\n```\nScanner says: \"Hardcoded API key\"\nActual code: const TEST_KEY = \"test-key-123\" in test\u002Ffixtures.ts\nVerdict: FALSE POSITIVE -- test fixture, not production code\nEvidence: File is in test directory, key is clearly a test value\nWARNING: Verify the key isn't a real key used in test environment\n```\n\n### 5. Intentional Behavior\n\n```\nScanner says: \"Insecure random number generation\"\nActual code: Math.random() used for UI animation timing\nVerdict: FALSE POSITIVE -- not used for security purposes\nEvidence: Used only for visual jitter in animation, no security impact\n```\n\n## Red Flags: When \"False Positive\" Is Actually Real\n\nDo NOT dismiss if:\n\n| Red Flag | Why It Matters |\n|----------|---------------|\n| \"It's behind a VPN\" | VPNs get compromised, zero trust is the standard |\n| \"Only admins can reach it\" | Admin accounts get compromised |\n| \"The input is from our other service\" | Services can be compromised too |\n| \"We sanitize it elsewhere\" | Verify the \"elsewhere\" actually runs |\n| \"It's just a low severity\" | Low severity findings chain into high impact |\n| \"The scanner is always wrong about this\" | Verify EACH instance independently |\n| \"We've never been exploited\" | Survivorship bias |\n\n## Verification Techniques\n\n### 1. Data Flow Tracing\nFollow the data from source to sink:\n```\nSource (user input) -> [validation?] -> [transformation?] -> [sanitization?] -> Sink (dangerous operation)\n\nIf ANY step is missing or bypassable, it's a TRUE POSITIVE.\n```\n\n### 2. Control Flow Analysis\nCheck all paths to the vulnerable code:\n```\nCan the code be reached without authentication?\nCan the code be reached with different parameters?\nCan the code be reached through an alternative route?\n```\n\n### 3. Exploit Attempt\nConstruct a minimal proof:\n```\nInput: [specific malicious input]\nExpected: [what should happen if vulnerable]\nActual: [what actually happens]\nBlocked by: [what prevents exploitation, if anything]\n```\n\n### 4. Historical Check\n```bash\n# Has this code had real vulnerabilities before?\ngit log --grep=\"fix\\|vuln\\|security\\|CVE\" -- \u003Cfile>\n\n# Has the scanner been wrong about this pattern before?\n# Check past triage decisions for this rule\n```\n\n## Batch Triage Template\n\nFor large scan results:\n\n```markdown\n# Security Scan Triage - [Date]\n\nScanner: [tool name and version]\nScan target: [repo\u002Fbranch\u002Fcommit]\nTotal findings: [N]\n\n## Summary\n| Verdict | Count |\n|---------|-------|\n| True Positive | X |\n| True Positive (mitigated) | X |\n| False Positive | X |\n| Needs Investigation | X |\n\n## True Positives (Action Required)\n1. [SEVERITY] file.ts:42 -- [description] -- [recommended fix]\n\n## False Positives (Documented)\n1. file.ts:88 -- [reason it's false positive]\n\n## Needs Investigation\n1. file.ts:120 -- [what additional info is needed]\n```\n\n## Integration with vibecosystem\n\n- **security-reviewer agent**: Use fp-check after running security scans\n- **sast-scanner agent**: Triage Semgrep results with this methodology\n- **code-reviewer agent**: When flagging potential issues, verify first\n- **verifier agent**: Include false positive check in quality gate\n\nInspired by [Trail of Bits](https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills) fp-check plugin.\n","# False Positive Verification\n\nNot every finding is real. But dismissing a real finding as \"false positive\" is worse than investigating a false one. This skill provides a systematic approach to verify findings without bias.\n\n## Verification Process\n\n### Step 1: Reproduce the Claim\n\nBefore dismissing anything, attempt to confirm:\n\n```\nFINDING: SQL injection in \u002Fapi\u002Fusers\nCLAIM: User input reaches database query unsanitized\n\nVERIFICATION:\n1. Read the actual code at the reported location\n2. Trace the data flow from input to sink\n3. Check for sanitization\u002Fvalidation between input and sink\n4. Check for framework-level protections (ORM, parameterized queries)\n5. Attempt to construct an exploit payload\n```\n\n### Step 2: Evidence-Based Triage\n\n| Verdict | Criteria | Evidence Required |\n|---------|----------|-------------------|\n| TRUE POSITIVE | Vulnerability exists and is exploitable | Code path + exploit scenario |\n| TRUE POSITIVE (mitigated) | Vulnerability exists but other controls prevent exploitation | Code path + mitigation proof |\n| FALSE POSITIVE (provable) | Finding is wrong due to tool limitation | Specific reason why tool was wrong |\n| FALSE POSITIVE (contextual) | Code is technically flagged but context makes it safe | Context documentation |\n| NEEDS INVESTIGATION | Cannot determine without more analysis | What additional info is needed |\n\n### Step 3: Document the Decision\n\n```\nFINDING: [scanner\u002Fauditor finding description]\nSOURCE: [which tool\u002Fperson reported it]\nLOCATION: file.ts:42\n\nVERDICT: [TRUE POSITIVE | FALSE POSITIVE | NEEDS INVESTIGATION]\n\nEVIDENCE:\n  - [What you checked]\n  - [What you found]\n  - [Why you reached this conclusion]\n\nREASONING:\n  [Detailed explanation of why this is\u002Fisn't a real finding]\n\nCONFIDENCE: [HIGH | MEDIUM | LOW]\n  [If LOW, explain what would increase confidence]\n```\n\n## Common False Positive Patterns\n\n### 1. Scanner Doesn't Understand Context\n\n```\nScanner says: \"Hardcoded password detected\"\nActual code: const DEFAULT_LABEL = \"password\"\nVerdict: FALSE POSITIVE -- it's a UI label, not a credential\nEvidence: Variable is used only in form field label rendering\n```\n\n### 2. Framework Protection Not Recognized\n\n```\nScanner says: \"SQL injection in query\"\nActual code: db.query(\"SELECT * FROM users WHERE id = $1\", [userId])\nVerdict: FALSE POSITIVE -- parameterized query prevents injection\nEvidence: $1 is a parameter placeholder, userId is bound safely\n```\n\n### 3. Dead Code \u002F Unreachable Path\n\n```\nScanner says: \"XSS in renderUserInput()\"\nActual code: renderUserInput() exists but is never called\nVerdict: FALSE POSITIVE -- function is dead code\nEvidence: grep shows no callers; function should be removed anyway\nWARNING: Verify it's truly unreachable, not just unused currently\n```\n\n### 4. Test Code Flagged\n\n```\nScanner says: \"Hardcoded API key\"\nActual code: const TEST_KEY = \"test-key-123\" in test\u002Ffixtures.ts\nVerdict: FALSE POSITIVE -- test fixture, not production code\nEvidence: File is in test directory, key is clearly a test value\nWARNING: Verify the key isn't a real key used in test environment\n```\n\n### 5. Intentional Behavior\n\n```\nScanner says: \"Insecure random number generation\"\nActual code: Math.random() used for UI animation timing\nVerdict: FALSE POSITIVE -- not used for security purposes\nEvidence: Used only for visual jitter in animation, no security impact\n```\n\n## Red Flags: When \"False Positive\" Is Actually Real\n\nDo NOT dismiss if:\n\n| Red Flag | Why It Matters |\n|----------|---------------|\n| \"It's behind a VPN\" | VPNs get compromised, zero trust is the standard |\n| \"Only admins can reach it\" | Admin accounts get compromised |\n| \"The input is from our other service\" | Services can be compromised too |\n| \"We sanitize it elsewhere\" | Verify the \"elsewhere\" actually runs |\n| \"It's just a low severity\" | Low severity findings chain into high impact |\n| \"The scanner is always wrong about this\" | Verify EACH instance independently |\n| \"We've never been exploited\" | Survivorship bias |\n\n## Verification Techniques\n\n### 1. Data Flow Tracing\nFollow the data from source to sink:\n```\nSource (user input) -> [validation?] -> [transformation?] -> [sanitization?] -> Sink (dangerous operation)\n\nIf ANY step is missing or bypassable, it's a TRUE POSITIVE.\n```\n\n### 2. Control Flow Analysis\nCheck all paths to the vulnerable code:\n```\nCan the code be reached without authentication?\nCan the code be reached with different parameters?\nCan the code be reached through an alternative route?\n```\n\n### 3. Exploit Attempt\nConstruct a minimal proof:\n```\nInput: [specific malicious input]\nExpected: [what should happen if vulnerable]\nActual: [what actually happens]\nBlocked by: [what prevents exploitation, if anything]\n```\n\n### 4. Historical Check\n```bash\n# Has this code had real vulnerabilities before?\ngit log --grep=\"fix\\|vuln\\|security\\|CVE\" -- \u003Cfile>\n\n# Has the scanner been wrong about this pattern before?\n# Check past triage decisions for this rule\n```\n\n## Batch Triage Template\n\nFor large scan results:\n\n```markdown\n# Security Scan Triage - [Date]\n\nScanner: [tool name and version]\nScan target: [repo\u002Fbranch\u002Fcommit]\nTotal findings: [N]\n\n## Summary\n| Verdict | Count |\n|---------|-------|\n| True Positive | X |\n| True Positive (mitigated) | X |\n| False Positive | X |\n| Needs Investigation | X |\n\n## True Positives (Action Required)\n1. [SEVERITY] file.ts:42 -- [description] -- [recommended fix]\n\n## False Positives (Documented)\n1. file.ts:88 -- [reason it's false positive]\n\n## Needs Investigation\n1. file.ts:120 -- [what additional info is needed]\n```\n\n## Integration with vibecosystem\n\n- **security-reviewer agent**: Use fp-check after running security scans\n- **sast-scanner agent**: Triage Semgrep results with this methodology\n- **code-reviewer agent**: When flagging potential issues, verify first\n- **verifier agent**: Include false positive check in quality gate\n\nInspired by [Trail of Bits](https:\u002F\u002Fgithub.com\u002Ftrailofbits\u002Fskills) fp-check plugin.\n",{"name":5,"description":7},"main","70e1c350500ee750987420bbae48837afa906b7e","skills\u002Ffp-check","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis","https:\u002F\u002Fgithub.com\u002Frubicanjr","linktr.ee\u002Ffinanskodu","Industrial Engineer & CIO @FinansKodu. Architecting AI-driven financial agents and autonomous workflows. 🏗️ Building systems, not just prompts.","2026-06-09 13:50:15",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add rubicanjr\u002FFinCognis --skill fp-check",{"tool":56,"command":57},"bunx","bunx skills add rubicanjr\u002FFinCognis --skill fp-check",{"tool":59,"command":60},"pnpm","pnpm dlx skills add rubicanjr\u002FFinCognis --skill fp-check","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Ffp-check\u002FSKILL.md",true,[],[65,86,93,113,141,159],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":76,"publishedAt":37},"01M6NWS9DAXJTADT4T5MB49X8W","workflow-router","Goal-based workflow orchestration - routes tasks to specialist agents based on user goals","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-router\u002FSKILL.md",[71],{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[77,78,79,80,81,82,83,84,85],"workflow router","workflow","router","orchestration","goals","goal","user","workflow orchestration","tasks",{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":37},"01M6NWS3RETSC0SHP16HP66E14","wiring","Wiring Verification","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwiring\u002FSKILL.md",[],[88,36,25],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":102,"publishedAt":37},"01M6NWS0XW9CVQZBDA1EGW0TWC","websocket-patterns","Connection management, room patterns, reconnection strategies, message buffering, and binary protocol design.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fwebsocket-patterns\u002Fskill.md",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000015","视觉设计",[103,104,105,106,107,108,109,110,111,112],"websocket","patterns","websocket patterns","design","protocol","management","message","strategies","binary","connection",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":123,"publishedAt":37},"01M6NWRDQDX9ZNETAWRRMQWV52","visual-verdict","Screenshot comparison QA for frontend development. Takes a screenshot of the current implementation, scores it across multiple visual dimensions, and returns a structured PASS\u002FREVISE\u002FFAIL verdict with concrete fixes. Use when implementing UI from a design reference or verifying visual correctness.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fvisual-verdict\u002FSKILL.md",[119,122],{"categoryNo":120,"categoryName":121,"taxonomyType":74,"taxonomyTypeDesc":75},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":72,"categoryName":73,"taxonomyType":74,"taxonomyTypeDesc":75},[124,125,126,127,128,129,130,131,132,22,133,134,135,106,136,137,138,139,31,140],"visual","verdict","visual verdict","ui","across","revise","comparison","correctness","implementing","fixes","dimensions","frontend","development","qa","screenshot","returns","frontend development",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":147,"publishedAt":37},"01M6NWR8HSNRS7MNDK2J02QYMN","verification-loop","Comprehensive verification system covering build, types, lint, tests, security, and diff review before a PR.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fverification-loop\u002FSKILL.md",[],[148,149,36,150,151,29,152,153,154,155,156,157,158],"verification loop","loop","lint","review","pr","system","diff","build","tests","diff review","types",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":37},"01M6NWR4HHSFR0VR5EXFRWA747","vector-db-patterns","Embedding strategies, ANN algorithms, hybrid search, RAG chunking strategies, and reranking for semantic search and retrieval.","https:\u002F\u002Fgithub.com\u002Frubicanjr\u002FFinCognis\u002Fblob\u002Fmain\u002Fskills\u002Fvector-db-patterns\u002Fskill.md",[],[166,167,168,169,104,170,171,172,173,110,174,175,176,177,178,22,179,180],"vector db patterns","vector db","db","vector","semantic search","search","embedding strategies","algorithms","chunking","semantic","retrieval","embedding","Hybrid Search","hybrid","rag"]