Agent skill · Security

cosmos-vulnerability-scanner

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/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.

trailofbitsgithub.com/trailofbitsGitHub ↗
claude-codeCC-BY-SA-4.0
Install
npx skills add trailofbits/skills --skill cosmos-vulnerability-scanner --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 11
SKILL.md size: 11 KB
Bundled scripts: none
Path: plugins/building-secure-contracts/skills/cosmos-vulnerability-scanner/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 6,426
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Cosmos Vulnerability Scanner ## Purpose Scan 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. **Output directory**: defaults to `.bughunt_cosmos/`. If the user specifies a different directory in their prompt, use that instead. ## When to Use - Auditing Cosmos SDK modules (custom `x/` modules) - Reviewing CosmWasm smart contracts - Pre-launch security assessment of Cosmos chains - Investigating chain halt incidents ## When NOT to Use - Pure Solidity/EVM audits without Cosmos SDK — use Solidity-specific tools - CometBFT consensus engine internals — this covers SDK modules, not the consensus layer itself - General Go code review with no blockchain context - Cosmos SDK application logic that is not consensus-critical (e.g., CLI commands, REST endpoints) - CosmWasm contract-only audits on chains without custom SDK modules — use the CosmWasm checklist items alone ## Essential Principles 1. **Consensus path is king** — A b

What's inside
Steps it walks through
  1. Purpose
  2. When to Use
  3. When NOT to Use
  4. Essential Principles
  5. Scanning Workflow
  6. Phase 1: Discovery (synchronous)
  7. Phase 2: Parallel Vulnerability Scan
  8. Phase 3: Write Findings
  9. Phase 4: Verify Completeness
  10. Success Criteria
  11. Resources
Ships with 10 files
  • CHANGELOG.md
  • agents/openai.yaml
  • assets/trail-of-bits-mark.svg
  • resources/ADVANCED_VULNERABILITY_PATTERNS.md
  • resources/COSMWASM_VULNERABILITY_PATTERNS.md
  • resources/DISCOVERY.md
  • resources/EVM_VULNERABILITY_PATTERNS.md
  • resources/IBC_VULNERABILITY_PATTERNS.md
  • resources/STATE_VULNERABILITY_PATTERNS.md
  • resources/VULNERABILITY_PATTERNS.md
More from skills
All skills →
About this skill
What does the cosmos-vulnerability-scanner skill do?

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/ modules, reviewing IBC integrations, or assessing pre-launch chain security. Updated for SDK v0.53.x.

How do I install it?

Run `npx skills add trailofbits/skills --skill cosmos-vulnerability-scanner --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From trailofbits/skills, a repository with 6,426 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going