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/hon454/grimoire/now-whatnpx skills add hon454/grimoire --skill now-whatgit 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/now-what)<a href="https://agentmods.dev/skills/hon454/grimoire/now-what"><img src="https://agentmods.dev/badge/skills/hon454/grimoire/now-what.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.1 | $0.00038 | $0.02220 |
| Opus 5 | $0.00019 | $0.01110 |
| Sonnet 5 | $0.00008 | $0.00444 |
| Haiku 4.5 | $0.00004 | $0.00222 |
Grade A, and why
now-what 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 5d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Now What
Personal standup for an active workspace: inspect current-work signals, recommend the next action, and stop.
Use only when explicitly invoked as $now-what or "use the now-what skill".
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.
Include one short locale notice before the source notice. State the resolved locale and whether it came from session config, explicit override, or direct OS observation. If the host supports interim messages, send it before inspection; otherwise make it the first line of the final response.
Use the resolved locale for user-facing prose, including notices, section headings, labels, recommendation rationale, and first moves. Preserve code, commands, paths, branch names, issue IDs, PR titles, commit subjects, and other technical identifiers as written after applying the data-handling rules below.
Use tracker values from the Grimoire session config as default tracker hints
only. Explicit user refs and directly observed branch, PR, issue, or local diff
signals still take precedence.
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.
- 5d ago First seen · 238 lines · 38 tokens per session scan A d2c541ea5bf7
now-what is a skill published in the GitHub repository hon454/grimoire (2 stars, last pushed 17d ago), licensed MIT. It adds 38 tokens to every session and 2,220 once invoked, about $0.0002 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
database-migrations
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL, and common ORMs (Prisma, Drizzle, Kysely, Django, TypeORM, golang-migrate).
execute
Dispatch and execute implementation plans with TDD and checkpoints. Use when plan is ready. Parallel by default for independent tasks.
flutter-ui
Build Flutter UI from Figma MCP or image input. Scans src for design tokens (colors, sizes, text styles), existing components, and naming conventions before writing a single line of code. Never hard-codes values.
plan
Create graph-informed implementation plans before writing code. Use before any non-trivial task. Skip for small changes (≤2 files, <20 lines, no hub/bridge).
review
Plan-aware graph-enhanced code review before merge. CRITICAL issues block merge. Use after fix/verify.
serena
Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.