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 hon454/grimoire --skill issue-readiness-reviewgit clone --depth 1 https://github.com/hon454/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/hon454/grimoire/issue-readiness-review)<a href="https://agentmods.dev/skills/hon454/grimoire/issue-readiness-review"><img src="https://agentmods.dev/badge/skills/hon454/grimoire/issue-readiness-review/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/hon454/grimoire/issue-readiness-review"><img src="https://agentmods.dev/badge/skills/hon454/grimoire/issue-readiness-review.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.00021 | $0.03530 |
| Opus 5 | $0.00010 | $0.01765 |
| Sonnet 5 | $0.00004 | $0.00706 |
| Haiku 4.5 | $0.00002 | $0.00353 |
Grade A, and why
issue-readiness-review 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 9d 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Readiness Review
Review a tracker issue like a launch readiness check: ground the work item in available evidence, close every question that can be closed inside the boundary, and produce the tracker-ready update the evidence supports. Stop after the drafts.
Use only when explicitly invoked as $issue-readiness-review or "use the
issue-readiness-review skill".
Goal
Without mutating the tracker, decide whether the target is ready to become an
implementation issue. For Ready targets, resolve every open question that can
be resolved from in-boundary evidence, then produce a paste-ready new issue body
draft and a paste-ready change summary comment draft.
For Not ready, Needs human decision, or Access blocked targets, do not
produce a new issue body draft. Produce a paste-ready tracker comment draft that
explains the readiness finding, checked evidence, and smallest next
decision/source needed.
For Ready targets, the goal is zero resolvable open questions, not zero open
questions. Leave questions that require human judgment, inaccessible sources, or
out-of-scope research in the final draft with their reason.
Output Locale
Resolve the final-output locale before inspecting sources. Prefer output
values from the Grimoire session config cache created by the Grimoire
SessionStart hook. Treat the cache file, not hook stdout, as the session
config source of truth. Hook stdout may help locate the cache path, but it is
only diagnostic.
When the cache is available, use output.locale from the cached session config
and include output.locale_source in the locale notice. If no Grimoire session
config cache is available, continue by directly observing the host OS preferred
locale with deterministic local signals and note the missing session config
only if it changes confidence.
If the user explicitly requests a final-output locale with a valid locale tag, pass it as an explicit override to the Grimoire config resolver when available. The resolver does not interpret natural-language locale requests. If no valid locale tag is provided, use Grimoire session config or OS preferred locale detection. This is the only override. Do not infer the final-output locale from conversation prose, tracker text, this skill file, repository prose, tool output, copied templates, or quoted artifacts.
What ships with it
3 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.
- 9d ago First seen · 396 lines · 21 tokens per session scan A 01769cbde964
issue-readiness-review is a skill published in the GitHub repository hon454/grimoire (2 stars, last pushed 21d ago), licensed MIT. It adds 21 tokens to every session and 3,530 once invoked, about $0.0001 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
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
frappe-gameplan
Frappe Gameplan guidance for team discussions, projects, tasks, notes, decisions, async collaboration, permissions, and workspace workflows. Use when work touches Gameplan or planning/collaboration features in the Frappe ecosystem.
cheat-status
A project-progress checker that reads a state file and scans the current project before summarising its status. It produces a list of what to work on today.
delivery-document-package
A workflow for maintaining client-facing project delivery documents, especially Word files and related handoff materials. It covers items such as delivery lists, demo scripts, acceptance forms, change records, quotes, contracts, and documentation indexes.
gstack-spec
GStack spec method for turning fuzzy intent into an executable spec with goals, non-goals, acceptance criteria, risks, and downstream role boundaries.
gstack-unfreeze
GStack unfreeze method for safely resuming a previously frozen task with explicit resume criteria, allowed changes, and verification gates.