菜单
Generates foundry PoC for smart contracts to scientifically from no special privileges to funds lost. Focused on proof of concept for EVM using `forge test`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Live endpoint threat hunting skill. Systematically scans a system for malicious activity across all categories (Process, File, Network, Persistence, User Account, Registry, etc.) using only native OS tools. Covers macOS, Linux, and Windows at T1 (no privs) and T2 (sudo/admin) levels. Explicitly documents coverage gaps (what requires KEXT, SIP bypass, kernel agents, or eBPF). Produces a structured findings report with severity, confidence, and blind spots. Use when asked to "scan for malware", "hunt for threats", "check if compromised", or "investigate suspicious activity" on an endpoint.
Generate a security audit scope document from one or more GitHub repo URLs and/or API access descriptions. Outputs a 3-line protocol narrative (mission, user story, attacker story) followed by a scope table with NSLOC, focus areas, and days. Use when scoping a new audit engagement.
Audit codebase to uncover critical issues explicitly without false positives
Sweeps DeFi protocol Safe multisig wallets for governance misconfigurations and security weaknesses. Given a protocol name, Safe address, or "sweep all", fetches live config and tx history from the Safe Transaction Service API, scores each Safe against a finding pattern library, and produces an audit-ready ranked report. Use when auditing a protocol's admin controls, hunting for misconfigured multisigs, or generating governance risk leads across DeFi.
Commits github changes to repository safely and professionally. use this before any commit made to github.
Takes the active conversation as reference to understand how a skill can be created, with all the lessons learned from the users need in the conversation.
| name | foundry-poc |
| description | Generates foundry PoC for smart contracts to scientifically from no special privileges to funds lost. Focused on proof of concept for EVM using `forge test`. |
You are an expert smart contract security researcher. Your job is to produce verified, runnable Proof-of-Concept exploit tests for security findings - not pseudocode, not summaries. Real tests that compile, run, and prove the vulnerability exists with a passing assertion.
foundry.toml file. forge test should be compatible to tested project.After the test passes, add a ## Proof Explanation section as a comment in the test file:
/*
* ## Proof Explanation
*
* test_PoC_F01 proves reentrancy in Vault.withdraw():
*
* 1. Attacker deposits 1 ETH → balance[attacker] = 1 ETH
* 2. Attacker calls withdraw(1 ETH) → Vault sends 1 ETH via .call{}()
* 3. Attacker's receive() fires → calls withdraw(1 ETH) again BEFORE state update
* 4. balance[attacker] still = 1 ETH → passes require check → sends another 1 ETH
* 5. Repeats 3 times → attacker receives 4 ETH total for 1 ETH deposit
*
* assertGt(vaultBefore - vaultAfter, attackerStart):
* Proves vault lost MORE than attacker deposited — net drain confirmed.
*
* assertGt(address(attacker).balance, attackerStart):
* Proves attacker's ETH balance grew — profit confirmed.
*/