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.
git clone --depth 1 https://github.com/noirdoc-ai/mask-claude-pluginWrote 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/commands/noirdoc-ai/mask-claude-plugin/noirdoc-status)<a href="https://agentmods.dev/commands/noirdoc-ai/mask-claude-plugin/noirdoc-status"><img src="https://agentmods.dev/badge/commands/noirdoc-ai/mask-claude-plugin/noirdoc-status/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/commands/noirdoc-ai/mask-claude-plugin/noirdoc-status"><img src="https://agentmods.dev/badge/commands/noirdoc-ai/mask-claude-plugin/noirdoc-status.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.00019 | $0.00447 |
| Opus 5 | $0.00010 | $0.00224 |
| Sonnet 5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
noirdoc-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 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.
What it actually says
Report the current noirdoc state for this workspace. Run these checks and present the results as a compact table or bullet list:
-
noirdoc --version— CLI present? Which version? -
Read
.noirdoc/config.toml— does it exist?noirdoc.namespacenoirdoc.guard.enablednoirdoc.guard.protected_paths(full list)noirdoc.guard.allowlist(full list)
-
.noirdoc/cache/size:du -sh .noirdoc/cache/ 2>/dev/null -
Namespace summary (counts only — no real-name data):
noirdoc ns summary <ns>Prints per-entity-type counts as JSON (e.g.,
{"PERSON": 12, "IBAN_CODE": 3, "LOCATION": 7}). The mapping itself never leaves the CLI. Report the counts inline.On non-zero exit (namespace doesn't exist yet), fall back to:
noirdoc ns listIf
<ns>is absent from the list, report "Namespace mapping: not yet created (no redactions run)". This is the expected initial state —~/.noirdoc/namespaces/<ns>/is created on the first/noirdoc-redactrun.Never run
noirdoc ns show,noirdoc lookup,cat ~/.noirdoc/...,python -c 'from noirdoc...', or any other command whose stdout would contain real-name data. The guard hook blocks these anyway; the point is not to attempt them. If the user needs to inspect the raw mapping, tell them to runnoirdoc ns show <ns>themselves in a regular terminal outside Claude Code.
If any step fails because the workspace isn't set up (missing .noirdoc/config.toml), say so plainly and suggest /noirdoc-setup.
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 · 29 lines · 19 tokens per session scan A fe5cfb3a9bc1
noirdoc-status is a command published in the GitHub repository noirdoc-ai/mask-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 447 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 commands, from other repositories
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.
synthesise-reviews
Deduplicate and reconcile multiple completed review reports into one prioritised revision plan with conflicts and dependencies made explicit. Use when parallel reviewers have returned findings that need a single action sequence. Not for running the reviews; use $review-cluster.
verify-math
Verify a self-authored mathematical result end to end by routing claims across adversarial review, numerical falsification, symbolic or CAS checks, and Lean, then aggregating one report. Use when a theorem, proposition, conjecture, or paper-wide mathematical argument needs the appropriate combination of verification…
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.