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 skills add asterinas/KVerus --skill kverus-stripgit clone --depth 1 https://github.com/asterinas/KVerusWrote 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/asterinas/kverus/kverus-strip)<a href="https://agentmods.dev/skills/asterinas/kverus/kverus-strip"><img src="https://agentmods.dev/badge/skills/asterinas/kverus/kverus-strip/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/skills/asterinas/kverus/kverus-strip"><img src="https://agentmods.dev/badge/skills/asterinas/kverus/kverus-strip.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.05641 |
| Opus 5.5 | $0.00020 | $0.02256 |
| Sonnet 5.5 | $0.00010 | $0.01128 |
| Haiku 4.5 | $0.00005 | $0.00564 |
Grade A, and why
kverus-strip 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 12d 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 — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aggressively strip redundant proof code from a Verus codebase while keeping verification passing. Be as aggressive as possible — many proof blocks and assertions exist purely for human readability and are not needed for the SMT solver to succeed.
Preferred invocation:
$kverus-strip verify="<verification command>" target-dirs="<dir1,dir2>"
If verify is missing, ask for it before editing. If target-dirs is missing, first run the proof simplification script for changed files; ask for target-dirs only before doing broader manual proof-code stripping.
Arguments
verify(required): The full verification command, e.g.cargo verus focus my_crate.target-dirs(required for broader manual stripping): Comma-separated source directories or single.rsfiles to scan, e.g.src/,specs/orsrc/model/owners.rs. A path the script would otherwise need to discover can be passed directly here.function(optional): Comma-separated function short names to restrict stripping to, e.g.lemma_index_bounds. Only matching functions are processed; all others in the file are left untouched.base(optional): Git base ref for changed-file discovery, e.g.origin/main.
Shared Verus References
If understanding Verus proof constructs (proof blocks, ghost/tracked values, spec/proof functions) is needed before deciding deletions, read the relevant reference under ../kverus-common/references/ before editing.
Proof Simplification Script
For routine redundant proof-statement cleanup, prefer the bundled script before manual stripping:
. "$AGENT_DIR/kverus.env"
"$KVERUS_PYTHON" "$AGENT_DIR/skills/kverus-strip/scripts/simplify_proof.py" \
--base <git-base> \
--target-dir '<dir1,dir2>' \
--verify-command '<verification command>' \
--format-command '<format command>'
The script scans changed .rs files when no --target-dir or --file is provided. It simplifies at function scope, matches the src/refiner/simplifier.py policy, skips runtime assert!(...), never removes assert(false), skips functions containing admit, assume, or #[verifier::external_body] unless --deep-clean is set, removes one proof statement at a time, and keeps the removal only when verification still succeeds. The rlimit perf guard (revert a passing strip when the Z3 rlimit grew by more than --perf-factor, measured via verus --time) applies only to functions carrying an explicit #[verifier::rlimit(...)] budget — those have a real cap a strip could push toward. Every other function strips purely on pass/fail: rlimit growth is not checked and no baseline probe verify is spent. Pass --no-perf-guard to apply that pass/fail-only behavior everywhere. With tree-sitter-verus, candidates include standalone function-call statements in proof fn, proof {}, and assertion proof blocks; executable calls are extracted but never offered for deletion. tree-sitter-verus is required and the script errors out if it is missing. Use --dry-run to list candidates without editing. Each candidate prints one bare outcome line — ✓ removed mod.rs:218 assert(fid != id);, ✗ kept … (verify failed), ~ kept … (rlimit exceeded: N > Kx baseline M) — (DEBUG-level sink, shown by default; --quiet hides them; colored on a tty, symbols only when piped). The tqdm bar postfix carries the live ✓N ✗N tally plus the candidate currently being verified, so there is no separate trying line. Each file first logs stripping <path>: N function(s) so the short filename in outcome lines stays unambiguous; kept … lines end with the bare reason and no more detail than that.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago Changed · +63 lines 9fb65b67249d
- 1mo ago Changed · +33 lines 724976f8607a
- 1mo ago Changed f051d32e2f2a
- 1mo ago First seen · 356 lines · 50 tokens per session scan A 3e5bab256f06
kverus-strip is a skill published in the GitHub repository asterinas/KVerus (27 stars, last pushed 13d ago), licensed MIT. It adds 50 tokens to every session and 5,641 once invoked, about $0.0002 per session on Opus 5.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
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.
github-auth
Set up GitHub authentication for the agent using git (universally available) or the gh CLI. Covers HTTPS tokens, SSH keys, credential helpers, and gh auth — with a detection flow to pick the right method automatically.
ax-rust-signature
Use when writing Rust code with axllm for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.
ideation
Generate project ideas through creative constraints. Use when the user says 'I want to build something', 'give me a project idea', 'I'm bored', 'what should I make', 'inspire me', or any variant of 'I have tools but no direction'. Works for code, art, hardware, writing, tools, and anything that can be made.
discrawl
Archive and search Discord guild messages, threads, and members via the discrawl CLI. Supports bot API sync, local cache import, full-text and semantic search, and Git-backed NDJSON snapshots.