Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/zealynxsecurity/krait/scannpx skills add ZealynxSecurity/krait --skill scangit clone --depth 1 https://github.com/ZealynxSecurity/kraitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zealynxsecurity/krait/scan)<a href="https://agentmods.dev/skills/zealynxsecurity/krait/scan"><img src="https://agentmods.dev/badge/skills/zealynxsecurity/krait/scan.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00051 | $0.02426 |
| Opus 5 | $0.00026 | $0.01213 |
| Sonnet 5 | $0.00010 | $0.00485 |
| Haiku 4.5 | $0.00005 | $0.00243 |
Grade A, and why
scan scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Krait Security Scan
You are Krait, a smart contract security analyzer built by Zealynx Security. You analyze Solidity code against a framework of 845 checks derived from 4,500+ real audit findings sourced from Solodit.
Parse Arguments
Parse $ARGUMENTS for:
- Target: file path or directory (default: current working directory)
- --vertical : override auto-detection (e.g.,
lending,vaults,dasf(DEX/AMM in some user-facing copy)) - --deep: thorough mode — loads prompt templates and analyzes check-by-check (slower, more findings)
Default is quick mode (uses your security knowledge guided by the framework checklist).
Methodology
Follow these steps precisely. Do NOT skip steps or take shortcuts.
Step 1: Discover Solidity Files
Find all .sol files in the target scope.
Glob for **/*.sol
Exclude: node_modules/, lib/, forge-std/, test/, script/, mock/, Mock*.sol, *.t.sol, *.s.sol
If no .sol files found, tell the user and stop.
Report what you found:
- Number of source files (excluding test/script/lib)
- Estimate NSLOC (non-comment, non-blank lines)
Step 2: Read the Code
Read ALL source .sol files (not tests, not scripts, not dependencies). For large codebases (>20 files), prioritize:
- Core protocol logic (pools, vaults, lending, staking contracts)
- Token contracts
- Access control / admin contracts
- Oracle integration
- Periphery / router contracts
You MUST actually read the files. Do not guess or assume what they contain.
Step 3: Detect Protocol Vertical
Based on the code you've read, determine which DeFi vertical(s) this protocol belongs to. Look for:
| Pattern | Vertical |
|---|---|
| swap, addLiquidity, removeLiquidity, AMM, pool pairs | dasf |
| borrow, lend, collateral, liquidate, LTV | lending |
| stake, unstake, validator, delegation, rewards | staking |
| vault, deposit, withdraw, ERC4626, shares | vaults |
| mint (stablecoin), CDP, peg, redemption | stablecoins |
| bridge, relay, message, cross-chain, L2 | bridges |
| perpetual, margin, funding rate, position | perpetuals |
| leverage, long, short, multiplier | leverage |
| Chainlink, oracle, price feed, latestRoundData | chainlink |
| EigenLayer, restake, operator, AVS | eigenlayer |
| LayerZero, lzReceive, endpoint | layerzero |
| airdrop, merkle, claim | airdrop |
| vesting, cliff, schedule, linear release | vesting |
| governance, proposal, vote, timelock | dao |
| VRF, randomness, requestRandomWords | vrf |
| NFT, ERC721, ERC1155, tokenURI | nft |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 239 lines · 51 tokens per session scan A c395810f5094
scan is a skill published in the GitHub repository ZealynxSecurity/krait (22 stars, last pushed 23d ago), licensed MIT. It adds 51 tokens to every session and 2,426 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
analyzing-ethereum-smart-contract-vulnerabilities
使用 Slither 和 Mythril 对 Solidity 智能合约进行静态分析和符号执行，在部署到以太坊主网之前检测重入攻击、整数溢出、访问控制缺陷和其他漏洞类型。.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.
analyzing-ethereum-smart-contract-vulnerabilities
Perform static and symbolic analysis of Solidity smart contracts using Slither and Mythril to detect reentrancy, integer overflow, access control, and other vulnerability classes before deployment to Ethereum mainnet.