Borrowing it
Nothing to install: this file belongs to SioYooo/RepoGrammar. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SioYooo/RepoGrammar/main/.agents/skills/rust-quality/SKILL.mdgit clone --depth 1 https://github.com/SioYooo/RepoGrammarWrote 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/sioyooo/repogrammar/rust-quality)<a href="https://agentmods.dev/skills/sioyooo/repogrammar/rust-quality"><img src="https://agentmods.dev/badge/skills/sioyooo/repogrammar/rust-quality/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/sioyooo/repogrammar/rust-quality"><img src="https://agentmods.dev/badge/skills/sioyooo/repogrammar/rust-quality.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.00031 | $0.00352 |
| Opus 5.5 | $0.00012 | $0.00141 |
| Sonnet 5.5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
rust-quality 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 2mo 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.
What it actually says
Purpose
Maintain Rust correctness, deterministic tests, and minimal public API.
Trigger conditions
Use when editing Rust files under src/rust/, Cargo metadata, tests, CI quality
commands, or repository automation implemented in Rust.
Required reading
docs/development/testing.mddocs/architecture/dependency-rules.mddocs/development/repository-guard.md
Preconditions
- Confirm production dependencies are necessary now.
- Confirm
unsafeis not needed unless an accepted ADR permits it.
Step-by-step procedure
- Prefer explicit types and typed errors.
- Keep recoverable errors out of
panic!. - Avoid hidden global state and silent fallback.
- Keep public API minimal.
- Add deterministic tests under
src/. - Review dependency additions with an architecture or ADR update.
Required verification
cargo fmt --all -- --check
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo test --workspace --all-features
Documentation updates
Update testing docs, module map, dependency rules, or relevant specifications when Rust behavior or boundaries change.
Commit requirements
Commit code, tests, and docs together. Do not commit failed partial work as success.
Completion report
Report the exact Rust commands and results.
Failure and rollback handling
Do not add #[allow], skip tests, weaken lints, or hide warnings unless the
maintainer explicitly accepts the tradeoff in documentation.
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.
- 2mo ago First seen · 61 lines · 31 tokens per session scan A fa998f1310bf
rust-quality is a skill published in the GitHub repository SioYooo/RepoGrammar (0 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 352 once invoked, about $0.0001 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-31.
Other skills, from other repositories
architecture-audit
Systematic architecture audit and refactoring methodology for Rust + TypeScript codebases. Use when performing refactoring, cleanup, unification, code review, dead code removal, module reorganization, or tech debt elimination. Ensures no naming confusion, semantic overloading, hidden defaults, duplicate logic, or…
presentations
Build PowerPoint (PPTX) decks — pptxgenjs when Node is present, python-pptx when not; edit existing decks in place via OOXML — with visual QA before delivery.
test-harness
Generates pytest test suites with happy path, edge cases, error conditions, fixture scaffolding, mocks, async patterns. Triggers on: "generate tests", "write tests for", "test this function", "create test suite", "pytest for", "unit tests for", "mock strategy for".
cargo-fuzz
Sets up and runs cargo-fuzz, the standard fuzzing tool for Cargo-based Rust projects. Covers cargo fuzz init, the nightly toolchain requirement, fuzztarget! harnesses, Arbitrary-derived structured inputs, sanitizer options, cargo fuzz coverage, and reproducing a crash artifact. Use when fuzzing a Rust crate, writing a…
bevy-ecs-patterns
Use when writing Bevy (Rust ECS) game code - pin and respect the repo's minor version, plugins/systems/queries/resources, schedules with FixedUpdate and Time, states and run conditions, messages vs observers across versions, required components, testing systems with App::update and a manual time strategy, compile-time…
mockery-suite-tests
Use when writing Go tests that need test doubles or cover multiple cases - detect the repo's mocking approach (Mockery v3, gomock, hand-written testify mocks, fakes), table-driven cases, testify suites when the repo uses them, and real-Postgres tests for repository adapters.