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 Netcracker/qubership-ai-packages --skill rustdoc-authoringgit clone --depth 1 https://github.com/Netcracker/qubership-ai-packagesWrote 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/netcracker/qubership-ai-packages/rustdoc-authoring)<a href="https://agentmods.dev/skills/netcracker/qubership-ai-packages/rustdoc-authoring"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/rustdoc-authoring/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/netcracker/qubership-ai-packages/rustdoc-authoring"><img src="https://agentmods.dev/badge/skills/netcracker/qubership-ai-packages/rustdoc-authoring.svg" alt="Reviewed on agentmods" width="80" 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.00223 | $0.17931 |
| Opus 5 | $0.00112 | $0.08965 |
| Sonnet 5 | $0.00045 | $0.03586 |
| Haiku 4.5 | $0.00022 | $0.01793 |
Grade A, and why
rustdoc-authoring 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 today.
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 — 1,202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authoring a Rust doc comment
This skill governs what a comment says and in what order. Wording, tone, sentence length, and
dialect belong to english-developer-style: load it too, and defer to it on the prose. The two
compose: this skill picks the slots; that one writes the sentences.
It is the Rust sibling of javadoc-authoring and godoc-authoring and keeps their section
numbering, so a review that cites "§7b" means the same rubric in any of the three. Read this one for
Rust; do not translate either of the others in your head. The slot model transfers unchanged. Three
things do not, and they are the reason this file exists:
- Rust's type system carries much of what a Java or Go comment has to state in prose.
Optionis the nullability rule,Resultis the error list, ownership and&mutare the aliasing contract,SendandSyncare the threading model. §4 is mostly about what is left. - A doc example compiles and runs. The code in a doc comment is a test the build executes, so the strongest statement a Rust comment can make is a checked assertion rather than a claim (§6).
- Nothing formats a doc comment for you. Measured on rustfmt 1.8.0, stable rustfmt leaves doc
comments byte for byte alone: it does not reflow a 180-column line, does not normalize a list
marker, does not fix indentation.
wrap_commentsandformat_code_in_doc_commentsare nightly-only and off. Wheregofmtlets a Go author write content and forget layout, you own the layout here. Match the wrapping width the file already uses.
Everything measured below was measured on rustc, cargo 1.92.0, clippy 0.1.92, and rustfmt 1.8.0.
1. The correction that matters most
"Document the why, not the what" is half wrong for a doc comment, and the wrong half does the damage.
An inline // comment inside a function documents the why; it sits next to code the reader can
already see. A doc comment on an item documents the contract: what a caller may rely on, what an
implementer must guarantee, what holds before and after. That is a what at the level of a promise,
not a restatement of the code.
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.
- today Changed · -20 lines c958fe86a1d5
- 5d ago Changed · +274 lines · +12 tokens per session 1f341faa3152
- 10d ago First seen · 948 lines · 211 tokens per session scan A 2e1193a002fb
rustdoc-authoring is a skill published in the GitHub repository Netcracker/qubership-ai-packages (4 stars, last pushed today), licensed Apache-2.0. It adds 223 tokens to every session and 17,931 once invoked, about $0.0011 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-31.
Other skills, from other repositories
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
omh-rust
This is a Hermes-native rust workflow skill.
bevy-ecs
Structure a Bevy app around its Entity Component System: build the App with plugins, define Component/Resource types, write systems with Query/Res/Commands, filter and order systems, and use the Time resource for frame-rate-independent motion. Use when building or debugging a Bevy game in Rust — when the user mentions…
rust-project
Modern Rust project architecture guide for 2025. Use when creating Rust projects (CLI, web services, libraries). Covers workspace structure, error handling, async patterns, and idiomatic Rust best practices.
gcs-rust-download-object-api
Fix "DownloadObjectRequest not found" error in google-cloud-storage Rust crate. Use when: (1) Trying to download objects from GCS using the Rust SDK, (2) Looking for a download request type in http::objects::download module, (3) Compile error about missing type. The downloadobject method uses GetObjectRequest from the…
azure-keyvault-secrets-rust
Client library for Azure Key Vault Secrets — secure storage for passwords, API keys, and other secrets.