[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75C0ZEVK003NJ7TQ25Y9RQ2":3,"skill-same:01M75C0ZEVK003NJ7TQ25Y9RQ2":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75C0ZEVK003NJ7TQ25Y9RQ2","cairo-vulnerability-scanner",null,"Scans Cairo\u002FStarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcairo-vulnerability-scanner\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: cairo-vulnerability-scanner\ndescription: Scans Cairo\u002FStarkNet smart contracts for 6 critical vulnerabilities including felt252 arithmetic overflow, L1-L2 messaging issues, address conversion problems, and signature replay. Use when auditing StarkNet projects.\n---\n\n# Cairo\u002FStarkNet Vulnerability Scanner\n\n## 1. Purpose\n\nSystematically scan Cairo smart contracts on StarkNet for platform-specific security vulnerabilities related to arithmetic, cross-layer messaging, and cryptographic operations. This skill encodes 6 critical vulnerability patterns unique to Cairo\u002FStarkNet ecosystem.\n\n## 2. When to Use This Skill\n\n- Auditing StarkNet smart contracts (Cairo)\n- Reviewing L1-L2 bridge implementations\n- Pre-launch security assessment of StarkNet applications\n- Validating cross-layer message handling\n- Reviewing signature verification logic\n- Assessing L1 handler functions\n\n## 3. Platform Detection\n\n### File Extensions & Indicators\n- **Cairo files**: `.cairo`\n\n### Language\u002FFramework Markers\n```rust\n\u002F\u002F Cairo contract indicators\n#[contract]\nmod MyContract {\n    use starknet::ContractAddress;\n\n    #[storage]\n    struct Storage {\n        balance: LegacyMap\u003CContractAddress, felt252>,\n    }\n\n    #[external(v0)]\n    fn transfer(ref self: ContractState, to: ContractAddress, amount: felt252) {\n        \u002F\u002F Contract logic\n    }\n\n    #[l1_handler]\n    fn handle_deposit(ref self: ContractState, from_address: felt252, amount: u256) {\n        \u002F\u002F L1 message handler\n    }\n}\n\n\u002F\u002F Common patterns\nfelt252, u128, u256\nContractAddress, EthAddress\n#[external(v0)], #[l1_handler], #[constructor]\nget_caller_address(), get_contract_address()\nsend_message_to_l1_syscall\n```\n\n### Project Structure\n- `src\u002Fcontract.cairo` - Main contract implementation\n- `src\u002Flib.cairo` - Library modules\n- `tests\u002F` - Contract tests\n- `Scarb.toml` - Cairo project configuration\n\n### Tool Support\n- **Caracal**: Trail of Bits static analyzer for Cairo\n- Installation: `pip install caracal`\n- Usage: `caracal detect src\u002F`\n- **cairo-test**: Built-in testing framework\n- **Starknet Foundry**: Testing and development toolkit\n\n---\n\n## 4. How This Skill Works\n\nWhen invoked, I will:\n\n1. **Search your codebase** for Cairo files\n2. **Analyze each contract** for the 6 vulnerability patterns\n3. **Report findings** with file references and severity\n4. **Provide fixes** for each identified issue\n5. **Check L1-L2 interactions** for messaging vulnerabilities\n\n---\n\n## 5. Example Output\n\nWhen vulnerabilities are found, you'll get a report like this:\n\n```\n=== CAIRO\u002FSTARKNET VULNERABILITY SCAN RESULTS ===\n\n\n---\n\n## 5. Vulnerability Patterns (6 Patterns)\n\nI check for 6 critical vulnerability patterns unique to Cairo\u002FStarknet. For detailed detection patterns, code examples, mitigations, and testing strategies, see [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md).\n\n### Pattern Summary:\n\n1. **Unchecked Arithmetic** ⚠️ CRITICAL - Integer overflow\u002Funderflow in felt252\n2. **Storage Collision** ⚠️ CRITICAL - Conflicting storage variable hashes\n3. **Missing Access Control** ⚠️ CRITICAL - No caller validation on sensitive functions\n4. **Improper Felt252 Boundaries** ⚠️ HIGH - Not validating felt252 range\n5. **Unvalidated Contract Address** ⚠️ HIGH - Using untrusted contract addresses\n6. **Missing Caller Validation** ⚠️ CRITICAL - No get_caller_address() checks\n\nFor complete vulnerability patterns with code examples, see [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md).\n## 5. Scanning Workflow\n\n### Step 1: Platform Identification\n1. Verify Cairo language and StarkNet framework\n2. Check Cairo version (Cairo 1.0+ vs legacy Cairo 0)\n3. Locate contract files (`src\u002F*.cairo`)\n4. Identify L1-L2 bridge contracts (if applicable)\n\n### Step 2: Arithmetic Safety Sweep\n```bash\n# Find felt252 usage in arithmetic\nrg \"felt252\" src\u002F | rg \"[-+*\u002F]\"\n\n# Find balance\u002Famount storage using felt252\nrg \"felt252\" src\u002F | rg \"balance|amount|total|supply\"\n\n# Should prefer u128, u256 instead\n```\n\n### Step 3: L1 Handler Analysis\nFor each `#[l1_handler]` function:\n- [ ] Validates `from_address` parameter\n- [ ] Checks address != zero\n- [ ] Has proper access control\n- [ ] Emits events for monitoring\n\n### Step 4: Signature Verification Review\nFor signature-based functions:\n- [ ] Includes nonce tracking\n- [ ] Nonce incremented after use\n- [ ] Domain separator includes chain ID and contract address\n- [ ] Cannot replay signatures\n\n### Step 5: L1-L2 Bridge Audit\nIf contract includes bridge functionality:\n- [ ] L1 validates address \u003C STARKNET_FIELD_PRIME\n- [ ] L1 implements message cancellation\n- [ ] L2 validates from_address in handlers\n- [ ] Symmetric access controls L1 ↔ L2\n- [ ] Test full roundtrip flows\n\n### Step 6: Static Analysis with Caracal\n```bash\n# Run Caracal detectors\ncaracal detect src\u002F\n\n# Specific detectors\ncaracal detect src\u002F --detectors unchecked-felt252-arithmetic\ncaracal detect src\u002F --detectors unchecked-l1-handler-from\ncaracal detect src\u002F --detectors missing-nonce-validation\n```\n\n---\n\n## 6. Reporting Format\n\n### Finding Template\n```markdown\n## [CRITICAL] Unchecked from_address in L1 Handler\n\n**Location**: `src\u002Fbridge.cairo:145-155` (handle_deposit function)\n\n**Description**:\nThe `handle_deposit` L1 handler function does not validate the `from_address` parameter. Any L1 contract can send messages to this function and mint tokens for arbitrary users, bypassing the intended L1 bridge access controls.\n\n**Vulnerable Code**:\n```rust\n\u002F\u002F bridge.cairo, line 145\n#[l1_handler]\nfn handle_deposit(\n    ref self: ContractState,\n    from_address: felt252,  \u002F\u002F Not validated!\n    user: ContractAddress,\n    amount: u256\n) {\n    let current_balance = self.balances.read(user);\n    self.balances.write(user, current_balance + amount);\n}\n```\n\n**Attack Scenario**:\n1. Attacker deploys malicious L1 contract\n2. Malicious contract calls `starknetCore.sendMessageToL2(l2Contract, selector, [attacker_address, 1000000])`\n3. L2 handler processes message without checking sender\n4. Attacker receives 1,000,000 tokens without depositing any funds\n5. Protocol suffers infinite mint vulnerability\n\n**Recommendation**:\nValidate `from_address` against authorized L1 bridge:\n```rust\n#[l1_handler]\nfn handle_deposit(\n    ref self: ContractState,\n    from_address: felt252,\n    user: ContractAddress,\n    amount: u256\n) {\n    \u002F\u002F Validate L1 sender\n    let authorized_l1_bridge = self.l1_bridge_address.read();\n    assert(from_address == authorized_l1_bridge, 'Unauthorized L1 sender');\n\n    let current_balance = self.balances.read(user);\n    self.balances.write(user, current_balance + amount);\n}\n```\n\n**References**:\n- building-secure-contracts\u002Fnot-so-smart-contracts\u002Fcairo\u002Funchecked_l1_handler_from\n- Caracal detector: `unchecked-l1-handler-from`\n```\n\n---\n\n## 7. Priority Guidelines\n\n### Critical (Immediate Fix Required)\n- Unchecked from_address in L1 handlers (infinite mint)\n- L1-L2 address conversion issues (funds to zero address)\n\n### High (Fix Before Deployment)\n- Felt252 arithmetic overflow\u002Funderflow (balance manipulation)\n- Missing signature replay protection (replay attacks)\n- L1-L2 message failure without cancellation (locked funds)\n\n### Medium (Address in Audit)\n- Overconstrained L1-L2 interactions (trapped funds)\n\n---\n\n## 8. Testing Recommendations\n\n### Unit Tests\n```rust\n#[cfg(test)]\nmod tests {\n    use super::*;\n\n    #[test]\n    fn test_felt252_overflow() {\n        \u002F\u002F Test arithmetic edge cases\n    }\n\n    #[test]\n    #[should_panic]\n    fn test_unauthorized_l1_handler() {\n        \u002F\u002F Wrong from_address should fail\n    }\n\n    #[test]\n    fn test_signature_replay_protection() {\n        \u002F\u002F Same signature twice should fail\n    }\n}\n```\n\n### Integration Tests (with L1)\n```rust\n\u002F\u002F Test full L1-L2 flow\n#[test]\nfn test_deposit_withdraw_roundtrip() {\n    \u002F\u002F 1. Deposit on L1\n    \u002F\u002F 2. Wait for L2 processing\n    \u002F\u002F 3. Verify L2 balance\n    \u002F\u002F 4. Withdraw to L1\n    \u002F\u002F 5. Verify L1 balance restored\n}\n```\n\n### Caracal CI Integration\n```yaml\n# .github\u002Fworkflows\u002Fsecurity.yml\n- name: Run Caracal\n  run: |\n    pip install caracal\n    caracal detect src\u002F --fail-on high,critical\n```\n\n---\n\n## 9. Additional Resources\n\n- **Building Secure Contracts**: `building-secure-contracts\u002Fnot-so-smart-contracts\u002Fcairo\u002F`\n- **Caracal**: https:\u002F\u002Fgithub.com\u002Fcrytic\u002Fcaracal\n- **Cairo Documentation**: https:\u002F\u002Fbook.cairo-lang.org\u002F\n- **StarkNet Documentation**: https:\u002F\u002Fdocs.starknet.io\u002F\n- **OpenZeppelin Cairo Contracts**: https:\u002F\u002Fgithub.com\u002FOpenZeppelin\u002Fcairo-contracts\n\n---\n\n## 10. Quick Reference Checklist\n\nBefore completing Cairo\u002FStarkNet audit:\n\n**Arithmetic Safety (HIGH)**:\n- [ ] No felt252 used for balances\u002Famounts (use u128\u002Fu256)\n- [ ] OR felt252 arithmetic has explicit bounds checking\n- [ ] Overflow\u002Funderflow scenarios tested\n\n**L1 Handler Security (CRITICAL)**:\n- [ ] ALL `#[l1_handler]` functions validate `from_address`\n- [ ] from_address compared against stored L1 contract address\n- [ ] Cannot bypass by deploying alternate L1 contract\n\n**L1-L2 Messaging (HIGH)**:\n- [ ] L1 bridge validates addresses \u003C STARKNET_FIELD_PRIME\n- [ ] L1 bridge implements message cancellation\n- [ ] L2 handlers check from_address\n- [ ] Symmetric validation rules L1 ↔ L2\n- [ ] Full roundtrip flows tested\n\n**Signature Security (HIGH)**:\n- [ ] Signatures include nonce tracking\n- [ ] Nonce incremented after each use\n- [ ] Domain separator includes chain ID and contract address\n- [ ] Signature replay tested and prevented\n- [ ] Cross-chain replay prevented\n\n**Tool Usage**:\n- [ ] Caracal scan completed with no critical findings\n- [ ] Unit tests cover all vulnerability scenarios\n- [ ] Integration tests verify L1-L2 flows\n- [ ] Testnet deployment tested before mainnet\n","# Cairo\u002FStarkNet Vulnerability Scanner\n\n## 1. Purpose\n\nSystematically scan Cairo smart contracts on StarkNet for platform-specific security vulnerabilities related to arithmetic, cross-layer messaging, and cryptographic operations. This skill encodes 6 critical vulnerability patterns unique to Cairo\u002FStarkNet ecosystem.\n\n## 2. When to Use This Skill\n\n- Auditing StarkNet smart contracts (Cairo)\n- Reviewing L1-L2 bridge implementations\n- Pre-launch security assessment of StarkNet applications\n- Validating cross-layer message handling\n- Reviewing signature verification logic\n- Assessing L1 handler functions\n\n## 3. Platform Detection\n\n### File Extensions & Indicators\n- **Cairo files**: `.cairo`\n\n### Language\u002FFramework Markers\n```rust\n\u002F\u002F Cairo contract indicators\n#[contract]\nmod MyContract {\n    use starknet::ContractAddress;\n\n    #[storage]\n    struct Storage {\n        balance: LegacyMap\u003CContractAddress, felt252>,\n    }\n\n    #[external(v0)]\n    fn transfer(ref self: ContractState, to: ContractAddress, amount: felt252) {\n        \u002F\u002F Contract logic\n    }\n\n    #[l1_handler]\n    fn handle_deposit(ref self: ContractState, from_address: felt252, amount: u256) {\n        \u002F\u002F L1 message handler\n    }\n}\n\n\u002F\u002F Common patterns\nfelt252, u128, u256\nContractAddress, EthAddress\n#[external(v0)], #[l1_handler], #[constructor]\nget_caller_address(), get_contract_address()\nsend_message_to_l1_syscall\n```\n\n### Project Structure\n- `src\u002Fcontract.cairo` - Main contract implementation\n- `src\u002Flib.cairo` - Library modules\n- `tests\u002F` - Contract tests\n- `Scarb.toml` - Cairo project configuration\n\n### Tool Support\n- **Caracal**: Trail of Bits static analyzer for Cairo\n- Installation: `pip install caracal`\n- Usage: `caracal detect src\u002F`\n- **cairo-test**: Built-in testing framework\n- **Starknet Foundry**: Testing and development toolkit\n\n---\n\n## 4. How This Skill Works\n\nWhen invoked, I will:\n\n1. **Search your codebase** for Cairo files\n2. **Analyze each contract** for the 6 vulnerability patterns\n3. **Report findings** with file references and severity\n4. **Provide fixes** for each identified issue\n5. **Check L1-L2 interactions** for messaging vulnerabilities\n\n---\n\n## 5. Example Output\n\nWhen vulnerabilities are found, you'll get a report like this:\n\n```\n=== CAIRO\u002FSTARKNET VULNERABILITY SCAN RESULTS ===\n\n\n---\n\n## 5. Vulnerability Patterns (6 Patterns)\n\nI check for 6 critical vulnerability patterns unique to Cairo\u002FStarknet. For detailed detection patterns, code examples, mitigations, and testing strategies, see [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md).\n\n### Pattern Summary:\n\n1. **Unchecked Arithmetic** ⚠️ CRITICAL - Integer overflow\u002Funderflow in felt252\n2. **Storage Collision** ⚠️ CRITICAL - Conflicting storage variable hashes\n3. **Missing Access Control** ⚠️ CRITICAL - No caller validation on sensitive functions\n4. **Improper Felt252 Boundaries** ⚠️ HIGH - Not validating felt252 range\n5. **Unvalidated Contract Address** ⚠️ HIGH - Using untrusted contract addresses\n6. **Missing Caller Validation** ⚠️ CRITICAL - No get_caller_address() checks\n\nFor complete vulnerability patterns with code examples, see [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md).\n## 5. Scanning Workflow\n\n### Step 1: Platform Identification\n1. Verify Cairo language and StarkNet framework\n2. Check Cairo version (Cairo 1.0+ vs legacy Cairo 0)\n3. Locate contract files (`src\u002F*.cairo`)\n4. Identify L1-L2 bridge contracts (if applicable)\n\n### Step 2: Arithmetic Safety Sweep\n```bash\n# Find felt252 usage in arithmetic\nrg \"felt252\" src\u002F | rg \"[-+*\u002F]\"\n\n# Find balance\u002Famount storage using felt252\nrg \"felt252\" src\u002F | rg \"balance|amount|total|supply\"\n\n# Should prefer u128, u256 instead\n```\n\n### Step 3: L1 Handler Analysis\nFor each `#[l1_handler]` function:\n- [ ] Validates `from_address` parameter\n- [ ] Checks address != zero\n- [ ] Has proper access control\n- [ ] Emits events for monitoring\n\n### Step 4: Signature Verification Review\nFor signature-based functions:\n- [ ] Includes nonce tracking\n- [ ] Nonce incremented after use\n- [ ] Domain separator includes chain ID and contract address\n- [ ] Cannot replay signatures\n\n### Step 5: L1-L2 Bridge Audit\nIf contract includes bridge functionality:\n- [ ] L1 validates address \u003C STARKNET_FIELD_PRIME\n- [ ] L1 implements message cancellation\n- [ ] L2 validates from_address in handlers\n- [ ] Symmetric access controls L1 ↔ L2\n- [ ] Test full roundtrip flows\n\n### Step 6: Static Analysis with Caracal\n```bash\n# Run Caracal detectors\ncaracal detect src\u002F\n\n# Specific detectors\ncaracal detect src\u002F --detectors unchecked-felt252-arithmetic\ncaracal detect src\u002F --detectors unchecked-l1-handler-from\ncaracal detect src\u002F --detectors missing-nonce-validation\n```\n\n---\n\n## 6. Reporting Format\n\n### Finding Template\n```markdown\n## [CRITICAL] Unchecked from_address in L1 Handler\n\n**Location**: `src\u002Fbridge.cairo:145-155` (handle_deposit function)\n\n**Description**:\nThe `handle_deposit` L1 handler function does not validate the `from_address` parameter. Any L1 contract can send messages to this function and mint tokens for arbitrary users, bypassing the intended L1 bridge access controls.\n\n**Vulnerable Code**:\n```rust\n\u002F\u002F bridge.cairo, line 145\n#[l1_handler]\nfn handle_deposit(\n    ref self: ContractState,\n    from_address: felt252,  \u002F\u002F Not validated!\n    user: ContractAddress,\n    amount: u256\n) {\n    let current_balance = self.balances.read(user);\n    self.balances.write(user, current_balance + amount);\n}\n```\n\n**Attack Scenario**:\n1. Attacker deploys malicious L1 contract\n2. Malicious contract calls `starknetCore.sendMessageToL2(l2Contract, selector, [attacker_address, 1000000])`\n3. L2 handler processes message without checking sender\n4. Attacker receives 1,000,000 tokens without depositing any funds\n5. Protocol suffers infinite mint vulnerability\n\n**Recommendation**:\nValidate `from_address` against authorized L1 bridge:\n```rust\n#[l1_handler]\nfn handle_deposit(\n    ref self: ContractState,\n    from_address: felt252,\n    user: ContractAddress,\n    amount: u256\n) {\n    \u002F\u002F Validate L1 sender\n    let authorized_l1_bridge = self.l1_bridge_address.read();\n    assert(from_address == authorized_l1_bridge, 'Unauthorized L1 sender');\n\n    let current_balance = self.balances.read(user);\n    self.balances.write(user, current_balance + amount);\n}\n```\n\n**References**:\n- building-secure-contracts\u002Fnot-so-smart-contracts\u002Fcairo\u002Funchecked_l1_handler_from\n- Caracal detector: `unchecked-l1-handler-from`\n```\n\n---\n\n## 7. Priority Guidelines\n\n### Critical (Immediate Fix Required)\n- Unchecked from_address in L1 handlers (infinite mint)\n- L1-L2 address conversion issues (funds to zero address)\n\n### High (Fix Before Deployment)\n- Felt252 arithmetic overflow\u002Funderflow (balance manipulation)\n- Missing signature replay protection (replay attacks)\n- L1-L2 message failure without cancellation (locked funds)\n\n### Medium (Address in Audit)\n- Overconstrained L1-L2 interactions (trapped funds)\n\n---\n\n## 8. Testing Recommendations\n\n### Unit Tests\n```rust\n#[cfg(test)]\nmod tests {\n    use super::*;\n\n    #[test]\n    fn test_felt252_overflow() {\n        \u002F\u002F Test arithmetic edge cases\n    }\n\n    #[test]\n    #[should_panic]\n    fn test_unauthorized_l1_handler() {\n        \u002F\u002F Wrong from_address should fail\n    }\n\n    #[test]\n    fn test_signature_replay_protection() {\n        \u002F\u002F Same signature twice should fail\n    }\n}\n```\n\n### Integration Tests (with L1)\n```rust\n\u002F\u002F Test full L1-L2 flow\n#[test]\nfn test_deposit_withdraw_roundtrip() {\n    \u002F\u002F 1. Deposit on L1\n    \u002F\u002F 2. Wait for L2 processing\n    \u002F\u002F 3. Verify L2 balance\n    \u002F\u002F 4. Withdraw to L1\n    \u002F\u002F 5. Verify L1 balance restored\n}\n```\n\n### Caracal CI Integration\n```yaml\n# .github\u002Fworkflows\u002Fsecurity.yml\n- name: Run Caracal\n  run: |\n    pip install caracal\n    caracal detect src\u002F --fail-on high,critical\n```\n\n---\n\n## 9. Additional Resources\n\n- **Building Secure Contracts**: `building-secure-contracts\u002Fnot-so-smart-contracts\u002Fcairo\u002F`\n- **Caracal**: https:\u002F\u002Fgithub.com\u002Fcrytic\u002Fcaracal\n- **Cairo Documentation**: https:\u002F\u002Fbook.cairo-lang.org\u002F\n- **StarkNet Documentation**: https:\u002F\u002Fdocs.starknet.io\u002F\n- **OpenZeppelin Cairo Contracts**: https:\u002F\u002Fgithub.com\u002FOpenZeppelin\u002Fcairo-contracts\n\n---\n\n## 10. Quick Reference Checklist\n\nBefore completing Cairo\u002FStarkNet audit:\n\n**Arithmetic Safety (HIGH)**:\n- [ ] No felt252 used for balances\u002Famounts (use u128\u002Fu256)\n- [ ] OR felt252 arithmetic has explicit bounds checking\n- [ ] Overflow\u002Funderflow scenarios tested\n\n**L1 Handler Security (CRITICAL)**:\n- [ ] ALL `#[l1_handler]` functions validate `from_address`\n- [ ] from_address compared against stored L1 contract address\n- [ ] Cannot bypass by deploying alternate L1 contract\n\n**L1-L2 Messaging (HIGH)**:\n- [ ] L1 bridge validates addresses \u003C STARKNET_FIELD_PRIME\n- [ ] L1 bridge implements message cancellation\n- [ ] L2 handlers check from_address\n- [ ] Symmetric validation rules L1 ↔ L2\n- [ ] Full roundtrip flows tested\n\n**Signature Security (HIGH)**:\n- [ ] Signatures include nonce tracking\n- [ ] Nonce incremented after each use\n- [ ] Domain separator includes chain ID and contract address\n- [ ] Signature replay tested and prevented\n- [ ] Cross-chain replay prevented\n\n**Tool Usage**:\n- [ ] Caracal scan completed with no critical findings\n- [ ] Unit tests cover all vulnerability scenarios\n- [ ] Integration tests verify L1-L2 flows\n- [ ] Testnet deployment tested before mainnet\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fcairo-vulnerability-scanner",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill cairo-vulnerability-scanner",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill cairo-vulnerability-scanner",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill cairo-vulnerability-scanner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcairo-vulnerability-scanner\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"resources\u002FVULNERABILITY_PATTERNS.md","REFERENCE","参考文档",21282,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fcairo-vulnerability-scanner\u002Fresources\u002FVULNERABILITY_PATTERNS.md",[53,60,67,76,83,90],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":71,"licenseFileUrl":72,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]