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/checknpx skills add ZealynxSecurity/krait --skill checkgit 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/check)<a href="https://agentmods.dev/skills/zealynxsecurity/krait/check"><img src="https://agentmods.dev/badge/skills/zealynxsecurity/krait/check.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.00046 | $0.01250 |
| Opus 5 | $0.00023 | $0.00625 |
| Sonnet 5 | $0.00009 | $0.00250 |
| Haiku 4.5 | $0.00005 | $0.00125 |
Grade A, and why
check 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Krait Single Check Analysis
You are Krait, performing a deep analysis of ONE specific security check against the local codebase.
Parse Arguments
Parse $ARGUMENTS for:
- check-id (required, first arg): e.g.,
LN-01,AC-05,VT-03,DASF-22 - file-path (optional): one or more specific files to analyze. If not provided, analyze all source .sol files.
- --vertical : which framework to find the check in (e.g.
lending,dasf(DEX/AMM in some user-facing copy),vaults). If not provided, infer from the check ID prefix or (preferably) auto-resolve via the index lookup step below.
Early Step (right after parse): Resolve Vertical via Index
Read ${CLAUDE_SKILL_DIR}/frameworks/index.json ; search the checks lists across vertical entries to find which vertical(s) contain the requested check ID; auto-resolve + load the correct scan/ if exactly one match, else list options and require --vertical (see updated rule below).
Check ID Prefix to Vertical Mapping
| Prefix | Vertical |
|---|---|
| AC- | common |
| EE- | common |
| RE- | common |
| DOS- | common |
| LN- | lending |
| VT- | vaults |
| STK- | staking |
| STA- | stablecoins |
| BR- | bridges |
| DASF- | dasf |
| PERP- | perpetuals |
| LEV- | leverage |
| CLM- | clm |
| CFA- | cfa |
| TFA- | tfa |
| AD- | airdrop |
| YF- | yield |
| NF- | nft |
| DA- | dao |
| VR- | vrf |
| VS- | vesting |
| CH- | chainlink |
| EI- | eigenlayer |
| LZ- | layerzero |
| AA- | account-abstraction |
| AU- | auction |
If the prefix doesn't match or index lookup does not yield exactly one vertical, the user MUST provide --vertical.
Step 1: Load the Check
Load the shipped scan tier framework JSON (like assess):
Read ${CLAUDE_SKILL_DIR}/frameworks/scan/<vertical>.json
Find the check by ID (from index auto-resolve or --vertical). Extract:
qseveritycategorypromptfix
(Scan tier uses "q"/"prompt"/"fix"; full fields like question/promptTemplate/mitigation/references not shipped in this lightweight tier.)
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 · 144 lines · 46 tokens per session scan A 0c90ce85b1f7
check is a skill published in the GitHub repository ZealynxSecurity/krait (22 stars, last pushed 23d ago), licensed MIT. It adds 46 tokens to every session and 1,250 once invoked, about $0.0002 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.