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 WilliamJnsson/NarratorDB --skill healthgit clone --depth 1 https://github.com/WilliamJnsson/NarratorDBWrote 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/williamjnsson/narratordb/health)<a href="https://agentmods.dev/skills/williamjnsson/narratordb/health"><img src="https://agentmods.dev/badge/skills/williamjnsson/narratordb/health/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/williamjnsson/narratordb/health"><img src="https://agentmods.dev/badge/skills/williamjnsson/narratordb/health.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.00037 | $0.00539 |
| Opus 5 | $0.00018 | $0.00269 |
| Sonnet 5 | $0.00007 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
health 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 11d 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.
What it actually says
Check NarratorDB health
Perform one quiet, read-only health check:
- Send one short progress update:
Checking NarratorDB health… - Call
statusexactly once withscope="project"andfull_check=false. - Interpret the structured response internally. Never echo its raw JSON.
- Inspect these fields before choosing the result:
health.ok;scope_diagnostics.project_writes_blocked;scope_diagnostics.warning;memory_counts.current_workspace;memory_counts.current_user_total.capture_policy.
- Finish with one concise line:
- blocked scope with healthy database:
NarratorDB's database is healthy, but project scope is unsafe: <brief warning>. Restart Codex from the intended project folder. - healthy and not blocked:
NarratorDB is healthy — <mode> mode with <capture_policy> capture; <current_workspace> memory/memories in this project, <current_user_total> total for you. - degraded database:
NarratorDB is degraded: <short reason>. <one recovery action>. - unavailable MCP:
NarratorDB is unavailable. Verify the installation, then restart Codex.
- blocked scope with healthy database:
When project_writes_blocked=true, describe database health and project-scope
safety separately. Never call project memory healthy or ready while that block
is active. Use the returned warning only as a brief explanation; the recovery
instruction must tell the user to restart Codex from the intended project
folder. If the warning is empty, use Codex started outside a confirmed project folder instead. If the database is also degraded, report both problems without
calling the database healthy.
When writes are not blocked but scope_diagnostics.warning is present, append
one short Scope warning: <warning>. clause to the healthy result. Do not list
database paths, user IDs, workspace IDs, health objects, timing fields, or
other counts unless the user asks for diagnostics.
Use correct singular/plural grammar for the two memory counts.
Do not call recall, resume, remember, remember_session, or forget.
Private mode needs no model-provider key. Never display environment contents or
secret values. Codex controls native status/spinner animation; this skill can
provide concise commentary but cannot customize that animation.
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.
- 11d ago First seen · 45 lines · 37 tokens per session scan A 0f9689c00a14
health is a skill published in the GitHub repository WilliamJnsson/NarratorDB (0 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 539 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…