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-fixgit 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-fix)<a href="https://agentmods.dev/skills/asterinas/kverus/kverus-fix"><img src="https://agentmods.dev/badge/skills/asterinas/kverus/kverus-fix/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-fix"><img src="https://agentmods.dev/badge/skills/asterinas/kverus/kverus-fix.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.01932 |
| Opus 5.5 | $0.00020 | $0.00773 |
| Sonnet 5.5 | $0.00010 | $0.00386 |
| Haiku 4.5 | $0.00005 | $0.00193 |
Grade A, and why
kverus-fix 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Verus verification failures by iterating edits and verification until the verification command succeeds.
Preferred invocation:
$kverus-fix target=path/to/entry.rs verify="<verification command>" error_message="<initial error message>" out_path=path/to/output
Automatic discovery:
$kverus-fix mode=auto
Enter automatic discovery mode when mode=auto is requested or either target or verify is missing; otherwise use explicit mode. Treat any supplied value as authoritative and discover only the missing value. Do not ask for missing inputs until the discovery procedure below has been exhausted.
Treat target as an entry file for diagnosis, not as the only file that may be edited.
If error_message is provided, use it as a first-pass hint, then always trust fresh output from the verification command.
If out_path is missing, use a reasonable workspace-local default path and report it.
Shared Verus References
Before adding verification annotations to executable functions or loops, read ../kverus-common/references/verus-syntax-quickref.md.
If a failure appears caused by Verus syntax, modes, ghost/tracked values, loop invariants, quantifiers, specialized solvers, or tokenized state-machine rules, read the relevant reference under ../kverus-common/references/ before editing.
If verification shows that a std, core, or alloc API has no applicable vstd specification, read both ../kverus-common/references/std-external-specifications.md and ../kverus-common/references/proof-engineering-and-trust-boundaries.md.
Objective
Given Verus code and its verification failure, produce a corrected version that passes verification while preserving proof intent.
Start from target, then modify only the smallest necessary dependency closure required to clear the verification failure.
Automatic Discovery Mode
Discover the verification command before the target so that the target is grounded in fresh diagnostics.
Discover the Verification Command
What ships with it
1 file 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.
- 1mo ago Changed 7d785e47d771
- 1mo ago First seen · 152 lines · 50 tokens per session scan A ca7315bc3141
kverus-fix is a skill published in the GitHub repository asterinas/KVerus (27 stars, last pushed 15d ago), licensed MIT. It adds 50 tokens to every session and 1,932 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
stack-trace-rust-probe
Internal helper for meta-stack-trace-investigator. Use when a Rust panic or backtrace needs Rust-specific Result/Option checks, cargo test guidance, and patch targets.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.
rust-tracing
Add or change Rust diagnostic tracing in litellm-rust, including route spans, subscriber layers, and Python logger delivery.
regex
Write, test, and debug regular expressions for pattern matching, search, and text extraction across programming languages. Use when the user asks to match patterns in text, validate input formats (email, URL, IP, phone, date), extract data with capture groups, build search patterns with lookahead or lookbehind, or…
code-analysis
LSP-based code analysis via mcpls MCP server. Use for compiler-accurate type inspection, go-to-definition, find-all-references, diagnostics, call hierarchy, workspace symbol search, code actions, rename refactoring, and document formatting. Provides real compiler errors — not guesses. Keywords: LSP, language server…
network
Network diagnostics, DNS lookup, port scanning, and connectivity testing. Use when the user asks to check if a host is reachable, trace network routes, resolve DNS records, inspect open ports, debug HTTP requests, check SSL/TLS certificates, test bandwidth, diagnose network latency, or troubleshoot connectivity issues…