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/jeffreytse/grimoire-core/missing-descriptionnpx skills add jeffreytse/grimoire-core --skill missing-descriptiongit clone --depth 1 https://github.com/jeffreytse/grimoire-coreWrote 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/jeffreytse/grimoire-core/missing-description)<a href="https://agentmods.dev/skills/jeffreytse/grimoire-core/missing-description"><img src="https://agentmods.dev/badge/skills/jeffreytse/grimoire-core/missing-description.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.00003 | $0.00191 |
| Opus 5 | $0.00002 | $0.00096 |
| Sonnet 5 | $0.00001 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
review-checklist 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.
This is a copy
88% identical to review-checklist — 1 line 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.
What it actually says
Review Checklist
Systematically verify every required step before signing off on a process.
Why This Is Best Practice
Adopted by: Aviation (FAA), surgery (WHO), NASA, nuclear power (NRC). Impact: WHO Surgical Safety Checklist reduced surgical complications by 36% and deaths by 47% (Haynes et al., NEJM 2009). Why best: Human memory under time pressure is unreliable. External checklists eliminate recall failures.
Sources: WHO Surgical Safety Checklist 2009, FAA Advisory Circular AC 120-21
Steps
- List every required step in sequence before beginning.
- Check each step immediately after performing it.
- Halt and resolve any step that fails before proceeding.
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 · 26 lines · 3 tokens per session scan A 7bce0aed46f9
review-checklist is a skill published in the GitHub repository jeffreytse/grimoire-core (4 stars, last pushed 15d ago), licensed MIT. It adds 3 tokens to every session and 191 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to review-checklist, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…
pg-migration
PostgreSQL schema migration safety reviewer and DDL generator. ALWAYS use when writing, reviewing, or planning PostgreSQL schema changes — ALTER TABLE, CREATE/DROP INDEX, column type changes, constraint additions, RLS policy changes, or any DDL touching production tables. Covers lock-level analysis, CREATE INDEX…
redis-cache-strategy
Redis caching strategy designer and reviewer. ALWAYS use when designing, reviewing, or troubleshooting Redis caching layers — cache pattern selection (cache-aside, write-through, write-behind), TTL strategy, cache stampede/penetration/avalanche prevention, hot key handling, cache-DB consistency, distributed locking…
systematic-debugging
Use when debugging, diagnosing, or investigating any bug, test failure, flaky test, race condition, unexpected behavior, build failure, production incident, third-party breakage, root cause analysis, or performance regression before proposing fixes.
google-search
Use when the user wants help finding information through Google or Google-style web search and expects more than raw links. Handle current facts, public-information lookups, official documents, tutorials, reports, tools, materials, or source discovery by classifying the search goal, generating precise queries…
research-first-development
Build knowledge bases that build software — research before code, teach before execute.