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-migrategit 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-migrate)<a href="https://agentmods.dev/skills/asterinas/kverus/kverus-migrate"><img src="https://agentmods.dev/badge/skills/asterinas/kverus/kverus-migrate/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-migrate"><img src="https://agentmods.dev/badge/skills/asterinas/kverus/kverus-migrate.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.00038 | $0.01458 |
| Opus 5.5 | $0.00015 | $0.00583 |
| Sonnet 5.5 | $0.00008 | $0.00292 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
kverus-migrate 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Convert Rust code into minimally modified Verus-compatible code for one explicit target file and verification command.
Preferred invocation:
$kverus-migrate target=path/to/file.rs verify="<verification command>"
If either target or verify is missing, ask for the missing value and stop.
Shared Verus References
If migration requires Verus syntax, modes, ghost/tracked values, atomic ghost code, loop invariants, or tokenized state-machine rules, read the relevant reference under ../kverus-common/references/ before editing.
Before adding, removing, or rewriting any executable Rust, read and follow
../kverus-common/references/exec-code-preservation.md.
Objective
Convert the Rust code in target into Verus-compatible code with the smallest possible set of edits such that:
- the code is syntactically accepted by Verus
- the verification command succeeds
- the original source structure is preserved as much as possible
- the result is suitable as a future proof-ready baseline, even if it is not fully proved now
The goal is not to fully verify semantic correctness. The goal is only to make the code pass at the syntax, compatibility, and front-end acceptance level.
Required Workflow
Before making large edits:
- inspect the target code and its immediate dependencies
- make a short plan
- edit incrementally
- run the verification command after meaningful changes
- use the error messages to guide the next minimal repair step
Avoid broad rewrites up front.
Hard Constraints
A. In-place edits only
Edit the code at the original location whenever possible.
Do not comment out an entire function, impl, or module and rewrite a replacement elsewhere if a local replacement is sufficient.
B. Preserve original Rust code locally
For every executable-code modification, follow the exact reason-first block-comment
format in ../kverus-common/references/exec-code-preservation.md. This requirement is
not optional when the original code can be recovered from the input or Git history.
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 · +6 lines 6a0f66520ad0
- 1mo ago First seen · 220 lines · 38 tokens per session scan A 7f53e93b294c
kverus-migrate is a skill published in the GitHub repository asterinas/KVerus (27 stars, last pushed yesterday), licensed MIT. It adds 38 tokens to every session and 1,458 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.
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.
ax-rust-signature
Use when writing Rust code with axllm for string signatures, field descriptors, JSON schema output, validation, and typed tool argument shapes.
ax-rust-llm
Use when writing Rust code with axllm for using the generated Ax package, factory functions, package docs, examples, and API reference.
vera-language
Write programs in the Vera programming language. Use when asked to write, edit, debug, or review Vera code (.vera files). Vera is a statically typed, purely functional language with algebraic effects, mandatory contracts, and typed slot references (@T.n) instead of variable names.
rust-string-enums
Define or refactor Rust string-valued enums and their Serde adapters in litellm-rust, using Strum and serdewith while preserving parsing, wire values, and schemas.