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 hex-plangit 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/hex-plan)<a href="https://agentmods.dev/skills/grimoire-rs/grimoire/hex-plan"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/hex-plan/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/hex-plan"><img src="https://agentmods.dev/badge/skills/grimoire-rs/grimoire/hex-plan.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.00099 | $0.04437 |
| Opus 5 | $0.00049 | $0.02218 |
| Sonnet 5 | $0.00020 | $0.00887 |
| Haiku 4.5 | $0.00010 | $0.00444 |
Grade A, and why
hex-plan 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 yesterday.
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.
This is a copy
86% identical to hex-architect — 551 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hex-plan — Planning Orchestrator
Thin dispatcher. It parses arguments, classifies the target's tier, resolves
overlays, runs the single meta-plan approval gate, announces the resolved
config, and hands off to the matching tier file. The phase plans live in
the five tier-<tier>.md files; the shared vocabulary
(tiers, the Review-Fix Loop, worker roles, model classes, the memory file)
lives in the hex-core reference library and is linked here, never
copied.
Shared contracts:
protocol.md ·
workers.md ·
models.md ·
memory.md.
If hex-core is not installed: grim add ghcr.io/michael-herwig/arcana/hex-core:latest.
Argument syntax
/hex-plan [tier] <target> [flags]
- tier (optional):
low | medium | high | xhigh | max | auto. Defaultauto— the classifier pickslow…xhigh.maxis explicit only —--tier=max, or a plan whose Status block saysTier: max; the classifier never emits it (protocol.md). - target (one of):
- free-text prompt;
<N>or#<N>— a number; probe PR first, fall back to issue;PR <N>/pull/<N>— an explicit pull request;issue <N>/issues/<N>— an explicit issue;- a full GitHub URL
https://github.com/<owner>/<repo>/(pull|issues)/<N>.
- flags (before the target, by convention):
--architect=inline|on— override the Design phase (seeoverlays.md).--research=skip|1|3— override Research breadth.--adversary/--no-adversary— force the cross-model plan-artifact pass on or off.--dry-run— make the meta-plan gate block for explicit approval and stop there (preview only, no workers launched).
Dispatch
The outer loop every hex orchestrator shares
(protocol.md):
What ships with it
7 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.
- yesterday First seen · 364 lines · 99 tokens per session scan A 63fc8a42ef20
hex-plan is a skill published in the GitHub repository grimoire-rs/grimoire (10 stars, last pushed 2d ago), licensed Apache-2.0. It adds 99 tokens to every session and 4,437 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to hex-architect, differing in 551 lines, and is treated as a copy.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.