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-redact)<a href="https://agentmods.dev/commands/noirdoc-ai/mask-claude-plugin/noirdoc-redact"><img src="https://agentmods.dev/badge/commands/noirdoc-ai/mask-claude-plugin/noirdoc-redact/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-redact"><img src="https://agentmods.dev/badge/commands/noirdoc-ai/mask-claude-plugin/noirdoc-redact.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.00021 | $0.00250 |
| Opus 5 | $0.00010 | $0.00125 |
| Sonnet 5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
noirdoc-redact 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
Redact the file at $ARGUMENTS using the namespace from .noirdoc/config.toml.
Steps:
- Verify
.noirdoc/config.tomlexists. If not, run/noirdoc-setupfirst (do not prompt — just tell the user and stop). - Read the
noirdoc.namespacevalue from the config. - Compute a 12-char sha256 hash of the input path to name the clean copy (
.noirdoc/cache/<hash>.<ext>). - Ensure
.noirdoc/cache/exists. - Run:
noirdoc redact --namespace <ns> "$ARGUMENTS" -o .noirdoc/cache/<hash>.<ext> - Report the path of the clean copy to the user. Do not read the original file afterwards.
If the user wants to also summarize/analyze/translate, this command does not do that — follow the round-trip workflow in the noirdoc skill from this point onward.
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 · 21 lines · 21 tokens per session scan A 4eac530b2064
noirdoc-redact is a command published in the GitHub repository noirdoc-ai/mask-claude-plugin (2 stars, last pushed 3mo ago), licensed MIT. It adds 21 tokens to every session and 250 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
venue-guidelines-compliance
Audit a paper and submission package against current official venue requirements for its venue, track, article type, cycle, and stage. Use when checking templates, limits, anonymity, declarations, or required files before submission or inside $pre-submission-report. Not for venue recommendations.
brief-compliance-check
Check a LaTeX coursework submission against the requirements in a supplied PDF assessment brief. Use when verifying format, required sections, word limits, or deliverables before submission. Not for general prose proofreading; use $proofread.
latex-posters
Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter. Use when the requested deliverable is a conference or research poster rather than sequential presentation slides. For slide decks, use $beamer-deck.
latex-scaffold
Convert an existing Markdown manuscript draft into a buildable LaTeX project with canonical structure and build configuration. Use when prose already exists but no LaTeX source tree does. Not for checking template drift in an existing project; use $latex-template.
split-pdf
Download, split, and deeply read an academic PDF that is not available through Paperpile. Use when a long external PDF needs page-wise ingestion. For Paperpile items, use the Paperpile text-extraction route instead.
pipeline-minutar-pdf
Pipeline completo de sentença judicial a partir de PDF (conversão, linha-tempo, relatório, análise, fundamentação, merge).