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/skills/noirdoc-ai/mask-claude-plugin/noirdoc)<a href="https://agentmods.dev/skills/noirdoc-ai/mask-claude-plugin/noirdoc"><img src="https://agentmods.dev/badge/skills/noirdoc-ai/mask-claude-plugin/noirdoc/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/noirdoc-ai/mask-claude-plugin/noirdoc"><img src="https://agentmods.dev/badge/skills/noirdoc-ai/mask-claude-plugin/noirdoc.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.00144 | $0.03144 |
| Opus 5 | $0.00072 | $0.01572 |
| Sonnet 5 | $0.00029 | $0.00629 |
| Haiku 4.5 | $0.00014 | $0.00314 |
Grade A, and why
noirdoc 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 10d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
noirdoc — privacy-preserving document workflow
This skill lets you work with sensitive local documents without pulling raw PII into your context. It orchestrates the noirdoc CLI: redact on the way in, reveal on the way out, so the user sees real names in your final output while your working context only holds placeholders like <<PERSON_1>> and <<IBAN_CODE_1>>.
When this applies
Use this skill when:
- The user asks you to read / summarize / translate / analyze / edit a document under
./incoming/,./clients/,./contracts/, or any file matching*.contract.*,*.nda.*,*.patient.*. - A
PreToolUseblock comes back with "noirdoc-protected" in the message. - The user says anything about "redact", "pseudonymize", "DSGVO", "PII", "GDPR", "anonymize names", "noirdoc", or German legal/HR/medical documents.
- The user drops a PDF/DOCX/XLSX of a contract, employment agreement, invoice, or similar into the workspace and asks you to work with it.
Don't use this skill when:
- The user's question is purely about code, configuration, or non-document files (source files, JSON configs that are clearly not PII).
- The file is already a redacted copy (look for
.noirdoc/cache/prefix, or placeholders like<<PERSON_1>>in a preview). - The user has explicitly told you the document contains no personal data and asked you to skip redaction — respect that, don't argue.
First-run setup
Before anything else, check whether this workspace is already set up:
test -f .noirdoc/config.toml && echo SETUP || echo NOT_SETUP
If NOT_SETUP, walk the user through setup before redacting anything:
-
Check noirdoc is installed.
noirdoc --version— if the command is not found, ask the user:"This workspace isn't set up for noirdoc yet. I can install it for you — the full German-first ensemble needs about 560 MB of disk (spaCy + Flair + GLiNER weights). Install noirdoc[full] now? (y/n)"
On yes:
pip install 'noirdoc[full]' && noirdoc models pullOn no: stop. Tell the user you can't proceed safely without the CLI, and offer to continue without redaction only if they explicitly accept that the document will enter your context in the clear.
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.
- 10d ago First seen · 159 lines · 144 tokens per session scan A 1ac25a1544bb
noirdoc is a skill published in the GitHub repository noirdoc-ai/mask-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 144 tokens to every session and 3,144 once invoked, about $0.0007 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
omh-report-package
This is a Hermes-native report-package workflow skill.
citra
Skill "citra" from SylphxAI/pdf-reader-mcp, covering citra — pdf evidence for agents, install, or, tools and sdk.
csv-to-sif
Export a project's FF&E product-library CSV as dealer-system SIF. Use to produce a .sif schedule; use sif-to-csv for the reverse direction.
product-data-cleanup
Clean a local FF&E CSV schedule by normalizing casing, dimensions, units, language, materials, and formatting. Use when asked to clean, fix, or standardize product data.
sif-to-csv
Parse a SIF (Standard Interchange Format) input into a readable preview and optionally append canonical product rows to the project's CSV library. Use when asked to convert or inspect SIF dealer data. For the reverse direction use /as:csv-to-sif.
product-data-import
Generate a formatted FF&E specification schedule from notes, CSV, or pasted lists and optionally save it to the project's 33-column CSV library. Use when asked to import products or build a schedule.