Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add noirdoc-ai/mask-claude-plugin/plugin install noirdocWrote 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-setup)<a href="https://agentmods.dev/commands/noirdoc-ai/mask-claude-plugin/noirdoc-setup"><img src="https://agentmods.dev/badge/commands/noirdoc-ai/mask-claude-plugin/noirdoc-setup.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.00020 | $0.00291 |
| Opus 5 | $0.00010 | $0.00146 |
| Sonnet 5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
noirdoc-setup 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 7d 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
Run the first-run setup flow documented in the noirdoc skill. The goal is to leave this workspace ready to use the round-trip redact/reveal workflow.
Steps (invoke the skill's "First-run setup" section for the full detail):
- Check
noirdoc --version. If missing, ask the user for consent and runpip install 'noirdoc[full]' && noirdoc models pull(warn about the ~560 MB download). - Suggest a namespace based on the current directory name and confirm with the user.
- Write
.noirdoc/config.tomlfrom the template at${CLAUDE_PLUGIN_ROOT}/templates/config.toml, substituting the chosen namespace. - Confirm the default protected-path list (
./incoming/**,./clients/**,./contracts/**,*.contract.*,*.nda.*). Edit before writing if the user wants a different set. - If this is a git repo, ensure
.noirdoc/cache/is in.gitignore. - Surface the privacy note: the namespace mapping at
~/.noirdoc/namespaces/<namespace>/is reversible and should be treated as sensitive.
If .noirdoc/config.toml already exists, confirm with the user before overwriting.
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.
- 7d ago First seen · 17 lines · 20 tokens per session scan A 925196d8dc9d
noirdoc-setup is a command published in the GitHub repository noirdoc-ai/mask-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 291 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.
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…
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.
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.