[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XK660REE3C0ARFEV1WCVR":3,"skill-same:01M79XK660REE3C0ARFEV1WCVR":88},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":27,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M79XK660REE3C0ARFEV1WCVR","cosmos-vulnerability-scanner",null,"Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x\u002F modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.","Heesho\u002Fraffle-fun","Heesho","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F100749457?v=4","01M79XHBVXHD5BHPJTHXK51VSC","01M79XHBWZQNAH0BTYT9A1RFCW",0,"MIT","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: cosmos-vulnerability-scanner\ndescription: \"Scans Cosmos SDK blockchain modules and CosmWasm contracts for consensus-critical vulnerabilities — chain halts, fund loss, state divergence. 25 core + 16 IBC + 10 EVM + 3 CosmWasm patterns. Use when auditing custom x\u002F modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.\"\n---\n\n# Cosmos Vulnerability Scanner\n\n## Purpose\n\nScan Cosmos SDK modules and CosmWasm contracts for vulnerabilities that cause chain halts, consensus failures, or fund loss. Spawns parallel scanning agents — each specializing in a vulnerability category — that return findings to the main skill, which then writes them as individual markdown files to an output directory.\n\n**Output directory**: defaults to `.bughunt_cosmos\u002F`. If the user specifies a different directory in their prompt, use that instead.\n\n## When to Use\n\n- Auditing Cosmos SDK modules (custom `x\u002F` modules)\n- Reviewing CosmWasm smart contracts\n- Pre-launch security assessment of Cosmos chains\n- Investigating chain halt incidents\n\n## When NOT to Use\n\n- Pure Solidity\u002FEVM audits without Cosmos SDK — use Solidity-specific tools\n- CometBFT consensus engine internals — this covers SDK modules, not the consensus layer itself\n- General Go code review with no blockchain context\n- Cosmos SDK application logic that is not consensus-critical (e.g., CLI commands, REST endpoints)\n- CosmWasm contract-only audits on chains without custom SDK modules — use the CosmWasm checklist items alone\n\n## Essential Principles\n\n1. **Consensus path is king** — A bug only matters for chain halt\u002Ffund loss if it's on the consensus-critical execution path (BeginBlock, EndBlock, FinalizeBlock, msg_server handlers, AnteHandler). Always verify a finding is reachable from consensus before reporting it.\n2. **State divergence = chain halt** — Any non-determinism that causes validators to compute different state roots will halt the chain. This is the highest-severity class because it affects all validators simultaneously.\n3. **Check the version** — Cosmos SDK has breaking changes across major versions (v0.47 removed GetSigners, v0.50 added ABCI 2.0, v0.53 deprecated ValidateBasic). Always check `go.mod` versions before applying patterns.\n4. **False positives waste audit time** — A map iteration in a CLI command is not a consensus bug. A panic in a query handler does not halt the chain. Verify the execution context before flagging.\n5. **Cross-module interactions are where bugs hide** — The most severe findings (IBC reentrancy, EVM\u002FCosmos state desync, authz escalation) involve interactions between modules, not bugs within a single module.\n\n## Scanning Workflow\n\n### Phase 1: Discovery (synchronous)\n\n**Entry**: Target codebase path provided by user. Codebase contains Go source (e.g., `x\u002F` modules, `go.mod`) or Rust contracts with `cosmwasm_std`.\n\nRun a **synchronous subagent** (Agent tool) with the full contents of [DISCOVERY.md](resources\u002FDISCOVERY.md) as its prompt. The agent must:\n\n1. Follow the Discovery workflow to explore the target codebase\n2. Return the full CLAUDE.md content (the technical inventory and threat model) in its response\n3. Return a structured summary with exactly these fields:\n\n```\nPLATFORM: pure-cosmos | evm | wasm        (pick one; if multiple, comma-separated)\nIBC_ENABLED: true | false\nSDK_VERSION: \u003Cversion from go.mod>\nIBC_GO_VERSION: \u003Cversion from go.mod, or \"n\u002Fa\">\nCUSTOM_MODULES: \u003Ccomma-separated list of x\u002F* modules>\n```\n\nAfter the subagent returns, **you** (the main skill) Write the CLAUDE.md to the target repo root. Save its path and the discovery values — these feed into Phase 2.\n\n**Exit**: CLAUDE.md written by main skill. PLATFORM, IBC_ENABLED, SDK_VERSION, IBC_GO_VERSION, and CUSTOM_MODULES captured.\n\n### Phase 2: Parallel Vulnerability Scan\n\nSpawn scanning agents **in a single message** for maximum parallelism. Use the Agent Prompt Template below, filling in the reference file for each agent. Subagents only need read access (Grep, Glob, Read) — they return findings in their response and the main skill writes the files.\n\n**Always spawn these 3 agents:**\n\n| Agent Name | Reference File | Scope |\n|------------|---------------|-------|\n| `core-scanner` | `VULNERABILITY_PATTERNS.md` | §1-9: non-determinism, ABCI, signers, validation, handlers, ante security |\n| `state-scanner` | `STATE_VULNERABILITY_PATTERNS.md` | §11-23: bookkeeping, bank, pagination, events, tx replay, governance, arithmetic, encoding, deprecated modules |\n| `advanced-scanner` | `ADVANCED_VULNERABILITY_PATTERNS.md` | §24-27: storage keys, consensus validation, circuit breaker, crypto |\n\n**Spawn conditionally (in the same parallel message):**\n\n| Agent Name | Condition | Reference File |\n|------------|-----------|---------------|\n| `evm-scanner` | PLATFORM includes `evm` | `EVM_VULNERABILITY_PATTERNS.md` |\n| `ibc-scanner` | IBC_ENABLED is `true` | `IBC_VULNERABILITY_PATTERNS.md` |\n| `cosmwasm-scanner` | PLATFORM includes `wasm` | `COSMWASM_VULNERABILITY_PATTERNS.md` |\n\n#### Agent Prompt Template\n\nConstruct each agent's prompt by replacing `{REFERENCE_FILE_PATH}` with the full path to the reference file (under `{baseDir}\u002Fresources\u002F`) and `{CLAUDE_MD_PATH}` with the path to the CLAUDE.md written in Phase 1:\n\n~~~\nPerform a very thorough security scan of a Cosmos SDK codebase for specific vulnerability patterns.\n\nCONTEXT:\nRead {CLAUDE_MD_PATH} for codebase context (SDK version, modules, threat model, key files).\n\nPATTERNS:\nRead {REFERENCE_FILE_PATH} — it contains numbered vulnerability patterns. For EACH pattern:\n1. Read the detection patterns and \"What to Check\" items\n2. Use Grep and Glob to search the target codebase for each pattern\n3. When a match is found, Read surrounding code to verify it's on a consensus-critical path (BeginBlock, EndBlock, FinalizeBlock, msg_server handlers, AnteHandler)\n4. Classify severity per the guidelines below\n\nRULES:\n- Consensus path only: Only flag code reachable from consensus-critical execution. CLI\u002Fquery\u002Ftest code is NOT a finding.\n- Check SDK version in go.mod before applying patterns (v0.47 removed GetSigners, v0.50 added ABCI 2.0, v0.53 deprecated ValidateBasic).\n- Always use the Grep tool for searches, not bash grep. The reference file contains search patterns — use them directly with the Grep tool.\n- Ignore cross-references to other resource files (e.g., links to IBC or COSMWASM patterns). Those patterns are covered by other scanning agents.\n- Reject these rationalizations:\n  - \"ValidateBasic catches this\" — deprecated and facultative since SDK v0.53\n  - \"Behind governance, so safe\" — governance proposals can be malicious\n  - \"IBC counterparty is trusted\" — any chain can open a channel\n  - \"Panic can't happen, input is validated\" — trace the full call chain\n  - \"Rounding error is only a few tokens\" — compounds over time, can be looped\n  - \"EVM precompile handles rollback\" — many have incomplete rollback\n\nSEVERITY:\n- Critical (fund loss): signer mismatch, broken bookkeeping, AnteHandler bypass, bank keeper misuse, IBC token inflation, EVM\u002FCosmos desync, Merkle proof forgery, arithmetic overflow\n- High (chain halt): non-determinism, ABCI panics, slow ABCI, non-deterministic IBC acks, consensus gaps, CacheContext event leak\n- Medium (DoS): unbounded pagination, tx replay, missing validation, governance spam, rate limiting, circuit breaker bypass, storage key collisions\n- Low (logic): rounding errors, stub handlers, event override, module ordering\n\nOUTPUT — RETURN FORMAT:\nDo NOT write any files. Return ALL findings and the summary in your response.\n\nFor each pattern, return one of:\n  §NUM PATTERN_NAME: Not applicable — [one-line reason]\n  §NUM PATTERN_NAME: FINDING (followed by the finding block below)\n\nFor each finding, include the full content using this template:\n\nFINDING_FILE: {SEVERITY}-s{SECTION_NUM}-{kebab-description}.md\n## [SEVERITY] Title\n**Location**: `file:line`\n**Description**: What the bug is and why it matters\n**Vulnerable Code**: [snippet]\n**Attack Scenario**: [numbered steps]\n**Recommendation**: How to fix\n**References**: [links to relevant advisories or building-secure-contracts]\n\nYou MUST report on ALL patterns in the reference file — do not skip any.\n~~~\n\n**Exit**: All scanning agents returned. Each reported on every pattern in their reference file.\n\n### Phase 3: Write Findings\n\nAfter all scanning agents return, write finding files to the output directory (default `.bughunt_cosmos\u002F`):\n\n1. Parse each agent's response for `FINDING_FILE:` blocks\n2. For each finding, Write the content to `{OUTPUT_DIR}\u002F{filename}` using the filename from `FINDING_FILE:`\n3. Create the output directory first if it doesn't exist\n\n### Phase 4: Verify Completeness\n\nAfter writing all findings, verify every pattern was assessed:\n\n1. Collect the summary lines (§NUM entries) returned by each agent\n2. Check pattern counts against expected totals:\n   - `core-scanner`: 8 patterns (§1-9, excluding §8 legacy-only)\n   - `state-scanner`: 13 patterns (§11-23)\n   - `advanced-scanner`: 4 patterns (§24-27)\n   - `evm-scanner` (if spawned): 10 patterns (§1-10)\n   - `ibc-scanner` (if spawned): 16 patterns (§1-16)\n   - `cosmwasm-scanner` (if spawned): 3 patterns (§1-3)\n3. If any pattern is missing from a summary, flag it and re-prompt that agent\n4. List all finding files written to the output directory with a `Glob` for `*.md`\n\n**Exit**: All patterns accounted for. Finding files listed for the user.\n\n---\n\n## Success Criteria\n\n- [ ] Discovery CLAUDE.md written with complete technical inventory and threat model\n- [ ] All scanning agents completed and reported on every pattern in their reference file\n- [ ] Pattern counts verified against expected totals (no patterns skipped)\n- [ ] All findings written to output directory as individual markdown files\n- [ ] Each finding file includes: severity, location, vulnerable code, attack scenario, recommendation\n\n---\n\n## Resources\n\n- **Discovery & CLAUDE.md**: [DISCOVERY.md](resources\u002FDISCOVERY.md)\n- **Core patterns (§1-9)**: [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md)\n- **State & module patterns (§11-23)**: [STATE_VULNERABILITY_PATTERNS.md](resources\u002FSTATE_VULNERABILITY_PATTERNS.md)\n- **Advanced patterns (§24-27)**: [ADVANCED_VULNERABILITY_PATTERNS.md](resources\u002FADVANCED_VULNERABILITY_PATTERNS.md)\n- **IBC vulnerabilities**: [IBC_VULNERABILITY_PATTERNS.md](resources\u002FIBC_VULNERABILITY_PATTERNS.md)\n- **CosmWasm vulnerabilities**: [COSMWASM_VULNERABILITY_PATTERNS.md](resources\u002FCOSMWASM_VULNERABILITY_PATTERNS.md)\n- **EVM vulnerabilities**: [EVM_VULNERABILITY_PATTERNS.md](resources\u002FEVM_VULNERABILITY_PATTERNS.md)\n- **Building Secure Contracts**: `building-secure-contracts\u002Fnot-so-smart-contracts\u002Fcosmos\u002F`\n- **Cosmos SDK Docs**: https:\u002F\u002Fdocs.cosmos.network\u002F\n- **CodeQL for Cosmos SDK**: https:\u002F\u002Fgithub.com\u002Fcrypto-com\u002Fcosmos-sdk-codeql\n","# Cosmos Vulnerability Scanner\n\n## Purpose\n\nScan Cosmos SDK modules and CosmWasm contracts for vulnerabilities that cause chain halts, consensus failures, or fund loss. Spawns parallel scanning agents — each specializing in a vulnerability category — that return findings to the main skill, which then writes them as individual markdown files to an output directory.\n\n**Output directory**: defaults to `.bughunt_cosmos\u002F`. If the user specifies a different directory in their prompt, use that instead.\n\n## When to Use\n\n- Auditing Cosmos SDK modules (custom `x\u002F` modules)\n- Reviewing CosmWasm smart contracts\n- Pre-launch security assessment of Cosmos chains\n- Investigating chain halt incidents\n\n## When NOT to Use\n\n- Pure Solidity\u002FEVM audits without Cosmos SDK — use Solidity-specific tools\n- CometBFT consensus engine internals — this covers SDK modules, not the consensus layer itself\n- General Go code review with no blockchain context\n- Cosmos SDK application logic that is not consensus-critical (e.g., CLI commands, REST endpoints)\n- CosmWasm contract-only audits on chains without custom SDK modules — use the CosmWasm checklist items alone\n\n## Essential Principles\n\n1. **Consensus path is king** — A bug only matters for chain halt\u002Ffund loss if it's on the consensus-critical execution path (BeginBlock, EndBlock, FinalizeBlock, msg_server handlers, AnteHandler). Always verify a finding is reachable from consensus before reporting it.\n2. **State divergence = chain halt** — Any non-determinism that causes validators to compute different state roots will halt the chain. This is the highest-severity class because it affects all validators simultaneously.\n3. **Check the version** — Cosmos SDK has breaking changes across major versions (v0.47 removed GetSigners, v0.50 added ABCI 2.0, v0.53 deprecated ValidateBasic). Always check `go.mod` versions before applying patterns.\n4. **False positives waste audit time** — A map iteration in a CLI command is not a consensus bug. A panic in a query handler does not halt the chain. Verify the execution context before flagging.\n5. **Cross-module interactions are where bugs hide** — The most severe findings (IBC reentrancy, EVM\u002FCosmos state desync, authz escalation) involve interactions between modules, not bugs within a single module.\n\n## Scanning Workflow\n\n### Phase 1: Discovery (synchronous)\n\n**Entry**: Target codebase path provided by user. Codebase contains Go source (e.g., `x\u002F` modules, `go.mod`) or Rust contracts with `cosmwasm_std`.\n\nRun a **synchronous subagent** (Agent tool) with the full contents of [DISCOVERY.md](resources\u002FDISCOVERY.md) as its prompt. The agent must:\n\n1. Follow the Discovery workflow to explore the target codebase\n2. Return the full CLAUDE.md content (the technical inventory and threat model) in its response\n3. Return a structured summary with exactly these fields:\n\n```\nPLATFORM: pure-cosmos | evm | wasm        (pick one; if multiple, comma-separated)\nIBC_ENABLED: true | false\nSDK_VERSION: \u003Cversion from go.mod>\nIBC_GO_VERSION: \u003Cversion from go.mod, or \"n\u002Fa\">\nCUSTOM_MODULES: \u003Ccomma-separated list of x\u002F* modules>\n```\n\nAfter the subagent returns, **you** (the main skill) Write the CLAUDE.md to the target repo root. Save its path and the discovery values — these feed into Phase 2.\n\n**Exit**: CLAUDE.md written by main skill. PLATFORM, IBC_ENABLED, SDK_VERSION, IBC_GO_VERSION, and CUSTOM_MODULES captured.\n\n### Phase 2: Parallel Vulnerability Scan\n\nSpawn scanning agents **in a single message** for maximum parallelism. Use the Agent Prompt Template below, filling in the reference file for each agent. Subagents only need read access (Grep, Glob, Read) — they return findings in their response and the main skill writes the files.\n\n**Always spawn these 3 agents:**\n\n| Agent Name | Reference File | Scope |\n|------------|---------------|-------|\n| `core-scanner` | `VULNERABILITY_PATTERNS.md` | §1-9: non-determinism, ABCI, signers, validation, handlers, ante security |\n| `state-scanner` | `STATE_VULNERABILITY_PATTERNS.md` | §11-23: bookkeeping, bank, pagination, events, tx replay, governance, arithmetic, encoding, deprecated modules |\n| `advanced-scanner` | `ADVANCED_VULNERABILITY_PATTERNS.md` | §24-27: storage keys, consensus validation, circuit breaker, crypto |\n\n**Spawn conditionally (in the same parallel message):**\n\n| Agent Name | Condition | Reference File |\n|------------|-----------|---------------|\n| `evm-scanner` | PLATFORM includes `evm` | `EVM_VULNERABILITY_PATTERNS.md` |\n| `ibc-scanner` | IBC_ENABLED is `true` | `IBC_VULNERABILITY_PATTERNS.md` |\n| `cosmwasm-scanner` | PLATFORM includes `wasm` | `COSMWASM_VULNERABILITY_PATTERNS.md` |\n\n#### Agent Prompt Template\n\nConstruct each agent's prompt by replacing `{REFERENCE_FILE_PATH}` with the full path to the reference file (under `{baseDir}\u002Fresources\u002F`) and `{CLAUDE_MD_PATH}` with the path to the CLAUDE.md written in Phase 1:\n\n~~~\nPerform a very thorough security scan of a Cosmos SDK codebase for specific vulnerability patterns.\n\nCONTEXT:\nRead {CLAUDE_MD_PATH} for codebase context (SDK version, modules, threat model, key files).\n\nPATTERNS:\nRead {REFERENCE_FILE_PATH} — it contains numbered vulnerability patterns. For EACH pattern:\n1. Read the detection patterns and \"What to Check\" items\n2. Use Grep and Glob to search the target codebase for each pattern\n3. When a match is found, Read surrounding code to verify it's on a consensus-critical path (BeginBlock, EndBlock, FinalizeBlock, msg_server handlers, AnteHandler)\n4. Classify severity per the guidelines below\n\nRULES:\n- Consensus path only: Only flag code reachable from consensus-critical execution. CLI\u002Fquery\u002Ftest code is NOT a finding.\n- Check SDK version in go.mod before applying patterns (v0.47 removed GetSigners, v0.50 added ABCI 2.0, v0.53 deprecated ValidateBasic).\n- Always use the Grep tool for searches, not bash grep. The reference file contains search patterns — use them directly with the Grep tool.\n- Ignore cross-references to other resource files (e.g., links to IBC or COSMWASM patterns). Those patterns are covered by other scanning agents.\n- Reject these rationalizations:\n  - \"ValidateBasic catches this\" — deprecated and facultative since SDK v0.53\n  - \"Behind governance, so safe\" — governance proposals can be malicious\n  - \"IBC counterparty is trusted\" — any chain can open a channel\n  - \"Panic can't happen, input is validated\" — trace the full call chain\n  - \"Rounding error is only a few tokens\" — compounds over time, can be looped\n  - \"EVM precompile handles rollback\" — many have incomplete rollback\n\nSEVERITY:\n- Critical (fund loss): signer mismatch, broken bookkeeping, AnteHandler bypass, bank keeper misuse, IBC token inflation, EVM\u002FCosmos desync, Merkle proof forgery, arithmetic overflow\n- High (chain halt): non-determinism, ABCI panics, slow ABCI, non-deterministic IBC acks, consensus gaps, CacheContext event leak\n- Medium (DoS): unbounded pagination, tx replay, missing validation, governance spam, rate limiting, circuit breaker bypass, storage key collisions\n- Low (logic): rounding errors, stub handlers, event override, module ordering\n\nOUTPUT — RETURN FORMAT:\nDo NOT write any files. Return ALL findings and the summary in your response.\n\nFor each pattern, return one of:\n  §NUM PATTERN_NAME: Not applicable — [one-line reason]\n  §NUM PATTERN_NAME: FINDING (followed by the finding block below)\n\nFor each finding, include the full content using this template:\n\nFINDING_FILE: {SEVERITY}-s{SECTION_NUM}-{kebab-description}.md\n## [SEVERITY] Title\n**Location**: `file:line`\n**Description**: What the bug is and why it matters\n**Vulnerable Code**: [snippet]\n**Attack Scenario**: [numbered steps]\n**Recommendation**: How to fix\n**References**: [links to relevant advisories or building-secure-contracts]\n\nYou MUST report on ALL patterns in the reference file — do not skip any.\n~~~\n\n**Exit**: All scanning agents returned. Each reported on every pattern in their reference file.\n\n### Phase 3: Write Findings\n\nAfter all scanning agents return, write finding files to the output directory (default `.bughunt_cosmos\u002F`):\n\n1. Parse each agent's response for `FINDING_FILE:` blocks\n2. For each finding, Write the content to `{OUTPUT_DIR}\u002F{filename}` using the filename from `FINDING_FILE:`\n3. Create the output directory first if it doesn't exist\n\n### Phase 4: Verify Completeness\n\nAfter writing all findings, verify every pattern was assessed:\n\n1. Collect the summary lines (§NUM entries) returned by each agent\n2. Check pattern counts against expected totals:\n   - `core-scanner`: 8 patterns (§1-9, excluding §8 legacy-only)\n   - `state-scanner`: 13 patterns (§11-23)\n   - `advanced-scanner`: 4 patterns (§24-27)\n   - `evm-scanner` (if spawned): 10 patterns (§1-10)\n   - `ibc-scanner` (if spawned): 16 patterns (§1-16)\n   - `cosmwasm-scanner` (if spawned): 3 patterns (§1-3)\n3. If any pattern is missing from a summary, flag it and re-prompt that agent\n4. List all finding files written to the output directory with a `Glob` for `*.md`\n\n**Exit**: All patterns accounted for. Finding files listed for the user.\n\n---\n\n## Success Criteria\n\n- [ ] Discovery CLAUDE.md written with complete technical inventory and threat model\n- [ ] All scanning agents completed and reported on every pattern in their reference file\n- [ ] Pattern counts verified against expected totals (no patterns skipped)\n- [ ] All findings written to output directory as individual markdown files\n- [ ] Each finding file includes: severity, location, vulnerable code, attack scenario, recommendation\n\n---\n\n## Resources\n\n- **Discovery & CLAUDE.md**: [DISCOVERY.md](resources\u002FDISCOVERY.md)\n- **Core patterns (§1-9)**: [VULNERABILITY_PATTERNS.md](resources\u002FVULNERABILITY_PATTERNS.md)\n- **State & module patterns (§11-23)**: [STATE_VULNERABILITY_PATTERNS.md](resources\u002FSTATE_VULNERABILITY_PATTERNS.md)\n- **Advanced patterns (§24-27)**: [ADVANCED_VULNERABILITY_PATTERNS.md](resources\u002FADVANCED_VULNERABILITY_PATTERNS.md)\n- **IBC vulnerabilities**: [IBC_VULNERABILITY_PATTERNS.md](resources\u002FIBC_VULNERABILITY_PATTERNS.md)\n- **CosmWasm vulnerabilities**: [COSMWASM_VULNERABILITY_PATTERNS.md](resources\u002FCOSMWASM_VULNERABILITY_PATTERNS.md)\n- **EVM vulnerabilities**: [EVM_VULNERABILITY_PATTERNS.md](resources\u002FEVM_VULNERABILITY_PATTERNS.md)\n- **Building Secure Contracts**: `building-secure-contracts\u002Fnot-so-smart-contracts\u002Fcosmos\u002F`\n- **Cosmos SDK Docs**: https:\u002F\u002Fdocs.cosmos.network\u002F\n- **CodeQL for Cosmos SDK**: https:\u002F\u002Fgithub.com\u002Fcrypto-com\u002Fcosmos-sdk-codeql\n",{"name":5,"description":7},"main","aa4fc8e4a5441efccc61aca4e77753a2e9f88c8b","audits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun","https:\u002F\u002Fraffle-fun-lake.vercel.app","https:\u002F\u002Fgithub.com\u002FHeesho","2026-10-22 13:02:00",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add Heesho\u002Fraffle-fun --skill cosmos-vulnerability-scanner",{"tool":36,"command":37},"bunx","bunx skills add Heesho\u002Fraffle-fun --skill cosmos-vulnerability-scanner",{"tool":39,"command":40},"pnpm","pnpm dlx skills add Heesho\u002Fraffle-fun --skill cosmos-vulnerability-scanner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002FSKILL.md",true,[44,50,56,60,64,68,72,76,80,84],{"path":45,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":48,"sourceHtmlUrl":49},"agents\u002Fopenai.yaml","REFERENCE","参考文档",256,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002Fagents\u002Fopenai.yaml",{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"assets\u002Ftrail-of-bits-mark.svg","ASSET","资产文件",3084,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002Fassets\u002Ftrail-of-bits-mark.svg",{"path":57,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":58,"sourceHtmlUrl":59},"CHANGELOG.md",12950,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002FCHANGELOG.md",{"path":61,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":62,"sourceHtmlUrl":63},"resources\u002FADVANCED_VULNERABILITY_PATTERNS.md",12800,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002Fresources\u002FADVANCED_VULNERABILITY_PATTERNS.md",{"path":65,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":66,"sourceHtmlUrl":67},"resources\u002FCOSMWASM_VULNERABILITY_PATTERNS.md",7643,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002Fresources\u002FCOSMWASM_VULNERABILITY_PATTERNS.md",{"path":69,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":70,"sourceHtmlUrl":71},"resources\u002FDISCOVERY.md",3018,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002Fresources\u002FDISCOVERY.md",{"path":73,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":74,"sourceHtmlUrl":75},"resources\u002FEVM_VULNERABILITY_PATTERNS.md",18442,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002Fresources\u002FEVM_VULNERABILITY_PATTERNS.md",{"path":77,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":78,"sourceHtmlUrl":79},"resources\u002FIBC_VULNERABILITY_PATTERNS.md",28119,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002Fresources\u002FIBC_VULNERABILITY_PATTERNS.md",{"path":81,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":82,"sourceHtmlUrl":83},"resources\u002FSTATE_VULNERABILITY_PATTERNS.md",29890,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002Fresources\u002FSTATE_VULNERABILITY_PATTERNS.md",{"path":85,"resourceType":46,"resourceTypeDesc":47,"sizeBytes":86,"sourceHtmlUrl":87},"resources\u002FVULNERABILITY_PATTERNS.md",27033,"https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fcosmos-vulnerability-scanner\u002Fresources\u002FVULNERABILITY_PATTERNS.md",[89,96,103,110,115,122],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M79XNCGXQ9R07VAPFB1H1WNF","spec-to-code-compliance","Check code against the documentation that specifies it - which requirements hold, which the code contradicts, which are absent, and what the code does that no document mentions. Use when comparing an implementation against a whitepaper, protocol spec, or design document.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FOPENAI-TOB\u002Fattempt-02\u002FS5\u002Fresources\u002Fskills\u002Fspec-to-code-compliance\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M79XN7ADEZVW17912WC2CM7R","0xsimao-ai","Accounting-first smart contract security audit in the style of 0xSimao — maps the protocol's money model, then attacks it with 12 parallel lenses derived from his 869 published findings. Trigger on \"0xsimao ai\", \"0xsimao audit\", \"audit\", \"simao audit\", \"check this contract\", \"review for security\". Modes - default (full repo) or a specific filename.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FOPENAI-SIMAO\u002Fattempt-01\u002Fresources\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M79XN26B8ZCW79FATC4TSXA5","solidity-auditor","Security audit of Solidity code while you develop. Trigger on \"audit\", \"check this contract\", \"review for security\", \"loop mode\", \"run the auditor in loop mode\", \"run 3 passes\". Modes - default (full repo) or a specific filename. Loop mode runs several passes in one scan, each pass told what the earlier ones found, and ends in one combined report; it remembers findings between scans in a ledger.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FOPENAI-PASHOV\u002Fattempt-01\u002Fharness-reference\u002FSKILL.md",[],[],{"skillNo":111,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":18},"01M79XMX0BKWJN0T8HZEBWTB6P","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fspec-to-code-compliance\u002F2.0.2\u002Fskills\u002Fspec-to-code-compliance\u002FSKILL.md",[],[],{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":18},"01M79XMM06CBG09CMZ5N8PGAZ1","entry-point-analyzer","Analyzes smart contract codebases to identify state-changing entry points for security auditing. Detects externally callable functions that modify state, categorizes them by access level (public, admin, role-restricted, contract-only), and generates structured audit reports. Excludes view\u002Fpure\u002Fread-only functions. Use when auditing smart contracts (Solidity, Vyper, Solana\u002FRust, Move, TON, CosmWasm) or when asked to find entry points, audit flows, external functions, access control patterns, or privileged operations.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fentry-point-analyzer\u002F1.0.4\u002Fskills\u002Fentry-point-analyzer\u002FSKILL.md",[],[],{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":128,"publishedAt":18},"01M79XMCTG9288DZNAM1R3K2K2","ton-vulnerability-scanner","Scans TON (The Open Network) smart contracts for 3 critical vulnerabilities including integer-as-boolean misuse, fake Jetton contracts, and forward TON without gas checks. Use when auditing FunC contracts.","https:\u002F\u002Fgithub.com\u002FHeesho\u002Fraffle-fun\u002Fblob\u002Fmain\u002Faudits\u002F2026-10-21-r001\u002Fruns\u002FDAYBREAK-TOB\u002Fattempt-02\u002Fruntime\u002Fcodex-home\u002Fplugins\u002Fcache\u002Ftrailofbits\u002Fbuilding-secure-contracts\u002F1.2.2\u002Fskills\u002Fton-vulnerability-scanner\u002FSKILL.md",[],[]]