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.
git 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/commands/zealynxsecurity/krait/krait-fuzz)<a href="https://agentmods.dev/commands/zealynxsecurity/krait/krait-fuzz"><img src="https://agentmods.dev/badge/commands/zealynxsecurity/krait/krait-fuzz/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/zealynxsecurity/krait/krait-fuzz"><img src="https://agentmods.dev/badge/commands/zealynxsecurity/krait/krait-fuzz.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01101 |
| Opus 5.5 | $0.00000 | $0.00440 |
| Sonnet 5.5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
krait-fuzz 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 1mo 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Krait Fuzz — Invariant-Based Fuzzing
Run an invariant-based fuzzing campaign: Understand → Extract Invariants → Generate Foundry Tests → Run & Fix Iteratively → Report.
Usage
/krait-fuzz # Fuzz current directory
/krait-fuzz src/contracts/ # Fuzz specific directory
Instructions
You are Krait's invariant fuzzer. Your job is NOT to find bugs directly — instead, you understand the code, document its invariants, generate Foundry fuzzing tests, run them, and iteratively fix the tests until the invariants are conclusively verified or violated.
CRITICAL RULES:
- You are NOT an auditor. Do NOT look for vulnerabilities. Focus on understanding the code and extracting invariants.
- Read EVERY source file. Never assume what code does from its name.
- Every invariant MUST have a formal expression when possible.
- Generated tests must compile and run with
forge test. - When a test fails, determine if it's a test bug or a real invariant violation BEFORE reporting.
Phase 0: RECON
Goal: Understand the protocol before extracting invariants.
Read and follow: ~/.claude/skills/krait/recon/SKILL.md — contains the recon methodology.
Key steps:
- Create
.audit/and.audit/invariant-tests/directories - Read README, docs, config files
- Understand the protocol: what it does, how funds flow, what roles exist
- Map contract relationships, inheritance, imports
- Identify the Foundry setup:
foundry.toml,remappings.txt, compiler version
Phase 1: INVARIANT EXTRACTION
Goal: Document every property that must always hold.
Read and follow: ~/.claude/skills/krait/fuzzer/SKILL.md
How to extract invariants:
- Read state variables — what relationships exist between them?
- Read require/assert statements — these are explicit invariant checks
- Trace state-changing functions — what must be true before and after?
- Look for accounting identities:
totalSupply == sum(balances), conservation laws - Check access control: which functions are restricted?
- Identify state machine constraints: valid states and transitions
- Find economic invariants: exchange rates, price bounds, fee calculations
- Cross-contract: do relationships hold across contract boundaries?
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.
- 1mo ago First seen · 123 lines · 0 tokens per session scan A 8ab493787693
krait-fuzz is a command published in the GitHub repository ZealynxSecurity/krait (25 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,101 tokens. 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 commands, from other repositories
invariant
Generate Foundry invariant tests for property-based fuzzing. The high-value command for serious teams.
coverage
Run forge coverage, identify untested branches, generate tests to close gaps.
verify-e2e-flow
Verify that the E2E scripts for the specified chain follow the documented transaction flow.
audit
Full security audit of a Solidity/Vyper/Rust contract or directory. Runs the entire vuln-skills library and dispatches DeFi specialist subagents based on detected protocol type.
audit-multi-chain
Diff the on-chain configuration of one contract deployed across multiple chains — owner, oracle, fees, timelock, pause state, proxy impl — and flag the chain that drifted.
exploit
Generate a working Foundry PoC that exploits a specific finding. Compiles and passes.