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/grimoire-rs/grimoire/code-checknpx skills add grimoire-rs/grimoire --skill code-checkgit clone --depth 1 https://github.com/grimoire-rs/grimoireWhat 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.00035 | $0.00675 |
| Opus 5 | $0.00017 | $0.00338 |
| Sonnet 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 2d 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.
- 2d 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 (8 stars, last pushed 2d ago), licensed Apache-2.0. It adds 35 tokens to every session and 675 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
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
haiku
When writing a haiku for this bot, follow these conventions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.