All authors
Claude Skills by swarmsec-app
github.com/swarmsec-app7 skills0 installs10 views
- attack-surfaceMaps the attack surface of Solidity contracts - state-changing entry points, who can call them, roles and admin powers, proxy and upgrade wiring, external calls and callbacks, oracle and token dependencies, and what cannot be resolved from the source. Use when the user asks for entry points, access control, privileged functions, trust boundaries or an architecture map before an audit. Produces a map, not vulnerability findings.Votes: 1
- auditEvidence-first security review of Solidity / EVM smart contracts (a file, a folder or a whole repository). Maps the attack surface, generates vulnerability hypotheses, has each one independently challenged, and writes a Markdown and JSON report. Use when the user asks to audit, security-review or find vulnerabilities in Solidity contracts, including quick single-contract checks answered in chat (the skill has a chat-only mode). Not for gas optimisation, style review or non-EVM code.Votes: 0
- defi-auditEconomic and cross-contract security review of DeFi Solidity code - vaults and share accounting, lending and liquidation, AMMs, oracles, staking and rewards, governance. Builds conservation and solvency properties, then tests attack hypotheses against them with explicit preconditions. Use when the user asks about economic attacks, oracle or price manipulation, flash-loan risk, share inflation, insolvency or reward accounting. For general Solidity bugs use the audit skill.Votes: 0
- diff-auditSecurity review of a Solidity change - a git range, commit, branch or uncommitted work, including proxy upgrades. Traces changed functions to their unchanged callers, compares storage layout and access modifiers between revisions, and separates issues the change introduced from ones that were already there. Use when the user asks to review a PR, diff, commit, upgrade or new implementation version for security.Votes: 0
- invariantsDerives security invariants for specific Solidity contracts (conservation, solvency, share accounting, authorization, nonce and replay rules) with their preconditions and excluded states, and on request writes Foundry invariant tests with handlers. Use when the user asks for invariants, properties to fuzz, a Foundry invariant suite, or what must always hold for a protocol.Votes: 0
- reportConsolidates a SwarmSec audit run directory into report.md and report.json - validates every finding against the schema and the source tree, deduplicates root causes, normalises severity, and renders the report. Use when the user asks to produce, regenerate or clean up the report for a SwarmSec run (for example `.swarmsec-audit/runs/latest`).Votes: 0
- verifyChallenges a suspected smart-contract vulnerability - from a SwarmSec finding file, another tool's report or the user's description - by tracing the exact path, trying to disprove it, and where permitted reproducing it with a local Foundry test in a sandbox copy. Ends with reproduced, supported, unresolved or rejected. Use when the user asks whether a reported Solidity bug is real, a false positive, exploitable, or wants a proof of concept.Votes: 0