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 grimoire-rs/grimoire --skill code-checkgit clone --depth 1 https://github.com/grimoire-rs/grimoireWrote 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/grimoire-rs/grimoire/code-check)<a href="https://agentmods.dev/skills/grimoire-rs/grimoire/code-check"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/code-check/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/grimoire-rs/grimoire/code-check"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/code-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high System Prompt Leakage · line 37 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00035 | $0.00675 |
| Opus 5.5 | $0.00014 | $0.00270 |
| Sonnet 5.5 | $0.00007 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
code-check 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codebase Health Auditor
Role: audit Grimoire code for Clean Code, SOLID, DRY, pattern consistency.
Workflow
- Fan out — launch one reviewer per audit dimension in parallel
- Audit — SOLID, DRY, smells, consistency, context-rule freshness
- Report — prioritized findings with file:line refs + remediation
Audit Dimensions
- SOLID — one responsibility per module, interface narrowness, dependency inversion
- DRY — knowledge duplication (MUST fix) vs incidental similarity (evaluate)
- Smells — long methods, god objects, primitive obsession, feature envy, message chains
- Consistency — error handling, async/await, naming, import strategy match existing patterns
- Context freshness — verify
subsystem-*.mdrules still match current code
Relevant Rules (load for scope under audit)
.claude/rules/quality-core.md— universal SOLID/DRY/YAGNI, severity tiers, review checklist.claude/rules/quality-rust.md— Rust block/warn-tier anti-patterns (.unwrap(),MutexGuard, blocking I/O,.clone()discipline, JoinSet, bounded channels).claude/rules/arch-principles.md— crate layout, pattern catalog, code style (descriptive type names, nomod.rs).claude/rules/subsystem-cli.md— CLI shell + single-table output rule.claude/rules/subsystem-cli-api.md— report data layer conventions.claude/rules/subsystem-file-structure.md— storage layout constraints
Tool Preferences
- Grep/Glob first — verify patterns before flagging
task duplo:diff— structural duplication scan (Rust-aware)cargo-geiger— unsafe code auditcargo-bloat— binary size hotspots
Output Format
## Codebase Health Report
### Executive Summary
**Health Score**: [A/B/C/D/F]
**Critical Issues**: [count]
### Pattern Violations
| Pattern | File:Line | Description | Remediation |
### SOLID Violations
| Principle | File:Line | Description | Remediation |
### Context Staleness
| Rule File | Stale Reference | Current State |
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 First seen · 78 lines · 35 tokens per session scan A 2eac30ba8e3f
code-check is a skill published in the GitHub repository grimoire-rs/grimoire (14 stars, last pushed today), licensed Apache-2.0. It adds 35 tokens to every session and 675 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
oracle
Oracle second-model review: bundle prompts/files, debug, refactor, design.
pr-review
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first.
pr-triage
First-touch triage for external pull requests - verdict, label, and a welcoming comment within minutes of open.
feedback-builder
Point Aeon at a service's /feedback endpoint - pull what agents reported (bugs, missing features), triage and cluster it, then build the best accepted request as a PR for a human to approve.
[REPLACE: SKILL_NAME]
First-touch review of newly opened PRs on [REPLACE: WATCHEDREPO] — verdict + welcoming comment + label.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.