grim-authoring

grim-authoring is a skill for Claude Code from grimoire-rs/grimoire. It costs 190 tokens per session (5,173 once invoked), scanned A, original, Apache-2.0.

A guide for creating, checking, and packaging artifacts that the Grim publishing tool can install, such as skills, rules, agents, MCP server descriptions, and bundles. It explains the required file formats and metadata for each kind.

In plain words
What is it for?
Use it when creating or editing Grim skills, rules, agent definitions, MCP server descriptors, or bundle TOML files, and when preparing them for build or release.
Why use it?
It helps avoid packaging the wrong files or missing required metadata when publishing artifacts to an OCI registry, a system for storing versioned packages.

Skill for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: reads .claude/ paths; mentions Claude Code; mentions Codex.

Good fit Use it when creating or editing Grim skills, rules, agent definitions, MCP server descriptors, or bundle TOML files, and when preparing them for build or release.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/grimoire-rs/grimoire/grim-authoring
Install

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.

Any agent
npx skills add grimoire-rs/grimoire --skill grim-authoring
Clone the repo
git clone --depth 1 https://github.com/grimoire-rs/grimoire

Made for: Claude Code.

Wrote 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.

agentmods badge for grim-authoring

README.md
[![agentmods](https://agentmods.dev/badge/skills/grimoire-rs/grimoire/grim-authoring/github.svg)](https://agentmods.dev/skills/grimoire-rs/grimoire/grim-authoring)
Your own site
<a href="https://agentmods.dev/skills/grimoire-rs/grimoire/grim-authoring"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/grim-authoring/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.

agentmods 80×15 button for grim-authoring

Your own site · 80×15
<a href="https://agentmods.dev/skills/grimoire-rs/grimoire/grim-authoring"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/grim-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 190 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,173 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00190 $0.05173
Opus 5.5 $0.00076 $0.02069
Sonnet 5.5 $0.00038 $0.01035
Haiku 4.5 $0.00019 $0.00517

Measured 2d ago against content hash 9b8101bf547f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

grim-authoring 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.

catalog/skills/grim-authoring/SKILL.md · 339 lines

How it starts

The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Grim Artifact Authoring

Grim publishes six artifact kinds to OCI registries. Each has its own source shape, frontmatter schema, and validation gates. This root file holds the invariants that apply to every kind; per-kind depth lives in references/, loaded via the routing table below.

The Six Kinds

grim build and grim release infer the kind from the path — except agents (always --kind agent, or they silently pack as rules) and MCP servers (always --kind mcp, or the .toml is treated as a bundle).

Kind Source shape Inference Installs as
Skill Directory with a SKILL.md index directory → skill Directory tree under the client's skills/ dir
Rule Single .md file .md → rule rules/<name>.md, per-client transform
Rule + support dir <name>.md + sibling <name>/ dir sibling dir auto-discovered Index file + rules/<name>/… side by side
Agent Single .md, frontmatter required never — --kind agent mandatory One agent file per client, per-client render
MCP server .toml descriptor with a [server] table never — --kind mcp mandatory Entry in each client's MCP config file, per-client render
Hook Directory with a hook.toml manifest + its payload files directory with hook.toml → hook Payload tree materialized once per scope, one recorded output per client. Arming is gated and off by default — see hook-spec.md
Bundle .toml member list .toml → bundle Never materializes — expands to its members

A skill directory or a rule's support directory can drop a .grimignore at its root (gitignore syntax) to keep runtime junk — __pycache__/, .venv/, .DS_Store — out of the pack and out of drift detection; a built-in default list already covers the common cases and .grimignore lines extend it; a !pattern line re-includes a default. SKILL.md, a rule's index, a hook's hook.toml, and .grimignore itself are never ignorable. A hook handler naming an ignored file fails grim build (65) — it would never be packed; its runtime byproducts beyond the defaults belong in .grimignore, or they read as drift. Agents get no .grimignore — their companion directory is already an allowlist. Full default list and semantics: [Artifact Reference § .grimignore][grimignore].

Read the full file on GitHub · 339 lines

Changes

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.

  1. 2d ago Changed · +21 lines · +28 tokens per session 9b8101bf547f
  2. 21d ago Changed · +93 lines · +21 tokens per session b2da67949c71
  3. 28d ago Changed · +15 lines 655287cb7fd9
  4. 1mo ago Changed · +3 tokens per session 1b5ff44bbfa8
  5. 1mo ago First seen · 210 lines · 138 tokens per session scan A 0d4fecc7b115

Subscribe to this mod's changes

grim-authoring is a skill published in the GitHub repository grimoire-rs/grimoire (14 stars, last pushed today), licensed Apache-2.0. It adds 190 tokens to every session and 5,173 once invoked, about $0.0008 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.