status

A command that reports whether the Notabene documentation review server is running and how many review comments are still open.

In plain words
What is it for?
Use it to check the server process, port, address, and count of unresolved comments for the current documentation project.
Why use it?
It gives a quick view of the review system's current state without requiring you to inspect its process, URL, or comment store manually.

Command

Install

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.

agentmods
npx agentmods add commands/z29k/notabene/status
Clone the repo
git clone --depth 1 https://github.com/z29k/notabene
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 189 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00189
Opus 5 $0.00011 $0.00095
Sonnet 5 $0.00004 $0.00038
Haiku 4.5 $0.00002 $0.00019

Measured 2d ago against content hash 505daf42770e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

status 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 2d 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.

packages/claude-plugin/commands/status.md · 14 lines

What it actually says

Report whether the notabene review server is running for this repo, and how many comments are open.

!node "${CLAUDE_PLUGIN_ROOT}/bin/nb.mjs" status $ARGUMENTS !node "${CLAUDE_PLUGIN_ROOT}/bin/nb.mjs" comments ls --open --json 2>/dev/null | node -e 'let s="";process.stdin.on("data",d=>s+=d).on("end",()=>{try{console.log("open comments:",JSON.parse(s).length)}catch{console.log("open comments: (store not readable)")}})'

Summarize: running or not (with the URL if running), and the open-comment count.

Changes

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.

  1. 2d ago First seen · 14 lines · 22 tokens per session scan A 505daf42770e

Subscribe to this mod's changes

status is a command published in the GitHub repository z29k/notabene (4 stars, last pushed 20d ago), licensed MIT. It adds 22 tokens to every session and 189 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.