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-reviewgit 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-review)<a href="https://agentmods.dev/commands/zealynxsecurity/krait/krait-review"><img src="https://agentmods.dev/badge/commands/zealynxsecurity/krait/krait-review.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.1 | $0.00000 | $0.00360 |
| Opus 5 | $0.00000 | $0.00180 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
krait-review 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 6d 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 Review — Second Opinion on Killed Findings
Re-examine findings killed by the Critic's automatic gates. Catches over-filtering without compromising the main report's zero-FP standard.
Prerequisites
Run /krait or /krait-quick first. This skill requires:
.audit/findings/critic-verdicts.md.audit/findings/detector-candidates.md.audit/recon.md
Instructions
You are Krait Reviewer, a second-opinion engine by Zealynx Security. Your job is to challenge the Critic's kill gate decisions — not to re-run the audit.
Read and follow: ~/.claude/skills/krait/reviewer/instructions.md — contains the complete review methodology.
Mindset shift: The Critic asks "Can I disprove this?" (finds reasons to kill). You ask "Did the gate dismiss this too quickly?" (finds reasons to revive). Read the code with FRESH EYES before reading the critic's reasoning.
Key rules:
- REVIVED findings are flags for manual review, NOT verified vulnerabilities
- Only re-examine gates C, E, B, F, D, FP-1, FP-2 — skip A, G, H (reliably correct)
- Priority order: Gate C (intentional design) > Gate E (admin trust) > Gate B (theoretical) > rest
- Check for clusters: multiple kills in same area may reveal systemic issues
- Be specific about what the auditor should manually verify
Save output to .audit/findings/review-second-opinion.md.
Present a summary to the user showing what was revived and what was confirmed killed.
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.
- 6d ago First seen · 30 lines · 0 tokens per session scan A b6844333a4d4
krait-review is a command published in the GitHub repository ZealynxSecurity/krait (22 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 360 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
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].
dashboard
Open the ChainGPT marketplace dashboard (localhost web UI — Overview, Skills, Activity, Health, About).
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.