Borrowing it
Nothing to install: this file belongs to ojCezarFerreira/Grimoire. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ojCezarFerreira/Grimoire/main/CLAUDE.mdgit clone --depth 1 https://github.com/ojCezarFerreira/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/instructions/ojcezarferreira/grimoire/claude-md)<a href="https://agentmods.dev/instructions/ojcezarferreira/grimoire/claude-md"><img src="https://agentmods.dev/badge/instructions/ojcezarferreira/grimoire/claude-md/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/instructions/ojcezarferreira/grimoire/claude-md"><img src="https://agentmods.dev/badge/instructions/ojcezarferreira/grimoire/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.04025 | $0.04025 |
| Opus 5 | $0.02013 | $0.02013 |
| Sonnet 5 | $0.00805 | $0.00805 |
| Haiku 4.5 | $0.00402 | $0.00402 |
Grade A, and why
Grimoire CLAUDE.md 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 8d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Note: this CLAUDE.md is for developers maintaining the Grimoire plugin. It is not loaded as context for end users — per Anthropic's plugin spec, a CLAUDE.md at the plugin root is ignored at install time. End-user context comes from the skills and from GRIMOIRE-CONVENTIONS.md.
What this repo is
A Claude Code plugin (.claude-plugin/plugin.json at the root) bundling eleven skills that define the Grimoire workflow: a disciplined Spec → Plan → Execute pipeline with a Quick fast-path, plus an Init step that establishes per-project context and an Update step that maintains the plugin itself.
Each skill is a single skills/<name>/SKILL.md file with YAML frontmatter (name, description, argument-hint) and a prompt body: skills/grimoire-init/SKILL.md, skills/grimoire-spec/SKILL.md, skills/grimoire-plan/SKILL.md, skills/grimoire-execute/SKILL.md, skills/grimoire-quick/SKILL.md, skills/grimoire-know/SKILL.md, skills/grimoire-update/SKILL.md, skills/grimoire-note/SKILL.md, skills/grimoire-deps/SKILL.md, skills/grimoire-construct/SKILL.md, skills/grimoire-construct-update/SKILL.md.
The shared, load-bearing workflow rules — TDD, sub-agent spawning, commits, .grimoire/ layout, project context, historic, pause points — live in a single source of truth: GRIMOIRE-CONVENTIONS.md. Each SKILL.md references it via ${CLAUDE_PLUGIN_ROOT}/GRIMOIRE-CONVENTIONS.md so the rules aren't duplicated across skill bodies.
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.
- 8d ago First seen · 61 lines · 4,025 tokens per session scan A c068b413614f
Grimoire CLAUDE.md is an instructions file published in the GitHub repository ojCezarFerreira/Grimoire (2 stars, last pushed 2mo ago), licensed MIT. It adds 4,025 tokens to every session, about $0.0201 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.