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/grim-usagenpx skills add grimoire-rs/grimoire --skill grim-usagegit 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/grim-usage)<a href="https://agentmods.dev/skills/grimoire-rs/grimoire/grim-usage"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/grim-usage.svg" alt="Measured on agentmods" 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 | $0.00122 | $0.02502 |
| Opus 5 | $0.00061 | $0.01251 |
| Sonnet 5 | $0.00024 | $0.00500 |
| Haiku 4.5 | $0.00012 | $0.00250 |
Grade A, and why
grim-usage 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 4d 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grim Usage
Grimoire (binary: grim) is a package manager for AI-agent configuration.
It distributes five artifact kinds — skills, rules, agents,
MCP servers, and bundles — through any standard OCI registry (GHCR,
Docker Hub, a private Distribution), with lockfile-pinned installs into a
growing fleet of AI clients plus a vendor-neutral agents target. The
current names are listed in
references/registries.md; the
set grows every minor release, so read it there rather than assuming. An
MCP server artifact installs by registering an entry in each client's
native MCP config file (never as a file of its own); uninstall removes
only that entry, never the file.
Not every client can host every kind: a skill is the one kind every client hosts, but a rule needs a per-file scoping surface, an agent needs a shipped file format, and an MCP server needs a config file grim can splice — and many clients lack one or more of those. Where a client cannot faithfully host a kind, grim warns and skips it, writing zero files. Most of the fleet declines rules and agents, and the skills-only clients write no MCP config at all. The authoritative per-client support matrix is the [Client Compatibility][clients] docs page — trust it over this summary, and check it rather than assuming.
Two consequences of that shape are worth knowing before your first
install. When nothing is detected, grim targets the generic agents
client — one copy into the shared .agents/skills pool — rather than
writing a directory for every client it knows about; a lock holding only
rules, agents, or MCP servers then has nowhere to go and exits 78. And
a client that reads that shared pool can be moved into it deliberately with
options.vendors.<name>.shared_skills. Both in
references/registries.md.
Verify Before Acting
Before composing any non-trivial grim command:
- Run
grim --version. This guide tracks the release it ships beside; on a different minor, treat every flag mentioned here as a hypothesis. - Run
grim <command> --helpbefore using flags you have not verified this session — it is the authoritative, always-current flag list. - On any conflict between this skill and live
--helpoutput, trust--help. It ships with the binary; this guide can lag.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 168 lines · 122 tokens per session scan A baa9510b0474
grim-usage is a skill published in the GitHub repository grimoire-rs/grimoire (8 stars, last pushed 4d ago), licensed Apache-2.0. It adds 122 tokens to every session and 2,502 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…