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 commands/zealynxsecurity/krait/krait-quickgit clone --depth 1 https://github.com/ZealynxSecurity/kraitWhat 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.00000 | $0.00237 |
| Opus 5 | $0.00000 | $0.00118 |
| Sonnet 5 | $0.00000 | $0.00047 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
krait-quick 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 2d 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.
What it actually says
Krait Quick — Fast Security Scan
Run a streamlined audit: Recon → Detection → Verification → Report. Skips state inconsistency analysis and cross-feed iteration for speed.
Instructions
Follow the /krait methodology but:
- Run Phase 0 (Recon) — full
- Run Phase 1 (Detection) — full
- Run Phase 1b (Rescan) — full, including its hard-exit rule
- SKIP Phase 1c (Per-Contract Analysis) entirely
- SKIP Phase 2 (State Analysis) entirely
- Run Phase 3 (Verification) — on detector + rescan candidates
- Run Phase 4 (Report) — full
This is ~2x faster but may miss state desynchronization bugs and per-contract depth findings.
Rescan is kept because it is the cheapest recall stage: 2 broad passes, and it self-skips entirely when Phase 1 produced nothing above Informational.
After the report, always show the web links banner from reporter instructions.md (krait.zealynx.io/report/findings and /dashboard links).
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.
- 2d ago First seen · 22 lines · 0 tokens per session scan A b286d2a4b2b9
krait-quick is a command published in the GitHub repository ZealynxSecurity/krait (22 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 237 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
dashboard
Open the ChainGPT marketplace dashboard (localhost web UI — Overview, Skills, Activity, Health, About).
deploy
Deploy Suwappu services on Railway. Usage: /deploy [prod|dev] [python-api|python-worker|terminal|api-ts|showcase|all].
status
Check what's actually running: Railway control plane + deep health + logs + CI. Usage: /status [prod|dev] [--quick].
audit
Attacker-minded security audit of scoped files. Traces auth + money-path data flows, streams compact findings incrementally (never one giant end-of-session JSON dump). Usage: /audit [attack-class].
worktree-check
Audit every git worktree for uncommitted, unpushed, or stashed work at risk before any reset/merge/cleanup. Usage: /worktree-check.
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.