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 skills/nevaberry/nevaberry-plugins/cargo-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill cargo-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWhat 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.00007 | $0.01816 |
| Opus 5 | $0.00003 | $0.00908 |
| Sonnet 5 | $0.00001 | $0.00363 |
| Haiku 4.5 | $0.00001 | $0.00182 |
Grade A, and why
cargo-knowledge-patch 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 3d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cargo Knowledge Patch
Use this skill when changing Cargo manifests, configuration, dependency workflows, builds, workspaces, packaging, publishing, Cargo scripts, or unstable Cargo features. Inspect the repository and installed toolchain before applying the guidance: project manifests, lockfiles, configuration, tests, and observed behavior take precedence.
Working method
- Run
cargo --versionand identify whether the repository pins a toolchain. - Inspect
Cargo.toml,Cargo.lock,.cargo/config.toml, workspace manifests, and CI commands relevant to the task. - Separate stable behavior from features that still require nightly Cargo
and
-Zflags. - Check the compatibility and removal notes before copying an older command line or configuration key.
- Open the task-specific reference from the index and preserve the repository's minimum supported Rust version.
- Validate manifest and configuration changes with the narrowest applicable Cargo command before running the full project test suite.
Reference index
| Reference | Topics |
|---|---|
| upgrades-and-compatibility.md | Security fixes, removals, deprecations, changed defaults, platform requirements, migration hazards |
| configuration-networking-and-cache.md | Configuration merging and includes, cache cleanup, Git and SSH, proxies, runners, warning policy |
| builds-targets-and-artifacts.md | Editions, targets, build directories, rustc and rustdoc, profiles, doctests, artifacts, cleaning |
| workspaces-dependencies-and-metadata.md | Workspaces, feature unification, dependency trees, metadata, vendoring, target filtering |
| packaging-publishing-and-registries.md | Package validation, archives, workspace publishing, registry data and APIs |
| scripts-build-scripts-and-subcommands.md | Cargo scripts, build-script environment and metadata, external subcommands, completions and help |
| unstable-analysis-and-lints.md | Build analysis, timings, SBOM data, Cargo lints, unit graphs, experimental build controls |
What ships with it
8 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.
- coverage.json 1.5 KB
- references/builds-targets-and-artifacts.md 5.9 KB
- references/configuration-networking-and-cache.md 4.7 KB
- references/packaging-publishing-and-registries.md 3.9 KB
- references/scripts-build-scripts-and-subcommands.md 3.7 KB
- references/unstable-analysis-and-lints.md 4.7 KB
- references/upgrades-and-compatibility.md 5.9 KB
- references/workspaces-dependencies-and-metadata.md 3.7 KB
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.
- 3d ago First seen · 219 lines · 7 tokens per session scan A de0f99747d9d
cargo-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 6d ago), licensed MIT. It adds 7 tokens to every session and 1,816 once invoked, about $0.0000 per session on Opus 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-network-module
Scaffold new Rust async networking modules for the nat464-sidecar project. Use when adding TCP/UDP listeners, protocol handlers, proxies, or translation modules. Triggers: 'scaffold module', 'add new module', 'create listener', 'create proxy', 'add protocol handler', 'new networking module', 'scaffold UDP', 'add ICMP…
verify
Self-healing verification loop (test → clippy → fmt).
rust-project-validate
运行 cargo fmt/clippy/build/e2e/test 验证项目规范；在每次任务结束前必须调用，重要的是必须在端到端测试之后执行，为提交代码做最后准备.
rust-review
Rust 服务审查：panic、SQL 注入、密钥、错误吞没、遗留标记.
rust-systems
Rust patterns for CLI tools, backend services, and general application code. Use when working with Rust, Cargo workspaces, axum/tokio services, clap CLIs, async concurrency, or configuring clippy, rustfmt, cargo-nextest, or Cargo.toml.
review-rust
Perform critical Rust code reviews covering correctness, edition 2024 compliance, error handling, API design, async pitfalls, and dependency hygiene. ALWAYS use this skill when the user wants to review, audit, or critically evaluate Rust code — whether that's a PR diff, a specific crate or module, a cross-cutting…