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/sioyooo/repogrammar/rust-qualitynpx skills add SioYooo/RepoGrammar --skill rust-qualitygit clone --depth 1 https://github.com/SioYooo/RepoGrammarWhat 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.00031 | $0.00352 |
| Opus 5 | $0.00015 | $0.00176 |
| Sonnet 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 yesterday.
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.
- yesterday 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 19d ago), licensed MIT. It adds 31 tokens to every session and 352 once invoked, about $0.0002 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
od-contribute
One-click contribution flow for OpenDesign (nexu-io/open-design) — even for non-coders. Pick one of four cards (ship a Skill or Design System you made with OD; translate docs; fix a typo / write a blog; report a bug), the agent validates and opens a PR (or issue) for you. Trigger words contribute to open design, ship…
clinical-case-report
Structured medical case presentation for clinical rounds, conferences, and documentation. Generates SOAP-format or narrative case reports with physiologically accurate vitals, labs, and evidence-based plans. Use when the brief mentions "case report", "case presentation", "SOAP note", "clinical case", "ward rounds"…
critique
Run a 5-dimension expert design review on any HTML artifact in the project — Philosophy / Visual hierarchy / Detail / Functionality / Innovation, each scored 0–10. Outputs a single self-contained HTML report with a radar chart, evidence-backed scores, and three lists: Keep / Fix / Quick-wins. Use when the brief asks…
github-dashboard
GitHub repository analytics dashboard — stars, forks, contributors, issues, pull requests, recent activity, and top contributors. Use when the brief asks for a GitHub repo dashboard, open-source growth report, repository health page, or GitHub analytics view.
dcf-valuation
Discounted cash flow valuation and intrinsic value analysis for public companies. Use when the brief asks for DCF, fair value, intrinsic value, price target, undervalued or overvalued analysis, or "what is this company worth?".
audio-jingle
Audio generation skill — jingles, beds, voiceover, and sound effects. Routes music requests to Suno V5 / Udio / Lyria, speech to MiniMax TTS / FishAudio / ElevenLabs V3, and SFX to ElevenLabs SFX or AudioCraft. Output is one MP3/WAV file saved to the project folder.