redaction-and-cleanup

redaction-and-cleanup is a skill for Claude Code from aneja5/forge-skills. It costs 63 tokens per session (1,121 once invoked), scanned A, original, MIT.

A cleanup process that copies documents for external sharing and replaces sensitive information with consistent placeholders while preserving the originals.

In plain words
What is it for?
Use it to prepare project artifacts for investors, partners, advisors, or external reviewers and record what was changed.
Why use it?
It reduces the risk of exposing private pricing, credentials, strategy, or other internal details when sharing files.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the forge-skills plugin — 42 skills, 36 commands, 1 hook shipped together

Good fit Use it to prepare project artifacts for investors, partners, advisors, or external reviewers and record what was changed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aneja5/forge-skills/redaction-and-cleanup
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.

Any agent
npx skills add aneja5/forge-skills --skill redaction-and-cleanup
Clone the repo
git clone --depth 1 https://github.com/aneja5/forge-skills

Made for: Claude Code.

Or install forge-skills, the plugin that ships this one along with the rest of its 42 skills, 36 commands, 1 hook.

Wrote 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.

agentmods badge for redaction-and-cleanup

README.md
[![agentmods](https://agentmods.dev/badge/skills/aneja5/forge-skills/redaction-and-cleanup/github.svg)](https://agentmods.dev/skills/aneja5/forge-skills/redaction-and-cleanup)
Your own site
<a href="https://agentmods.dev/skills/aneja5/forge-skills/redaction-and-cleanup"><img src="https://agentmods.dev/badge/skills/aneja5/forge-skills/redaction-and-cleanup/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.

agentmods 80×15 button for redaction-and-cleanup

Your own site · 80×15
<a href="https://agentmods.dev/skills/aneja5/forge-skills/redaction-and-cleanup"><img src="https://agentmods.dev/badge/skills/aneja5/forge-skills/redaction-and-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,121 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00063 $0.01121
Opus 5 $0.00032 $0.00561
Sonnet 5 $0.00013 $0.00224
Haiku 4.5 $0.00006 $0.00112

Measured 9d ago against content hash f38f82c221d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

redaction-and-cleanup 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.

skills/redaction-and-cleanup/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Redaction and Cleanup

Overview

Prepare .forge/ documents for external sharing by copying them to .forge/redacted/ and replacing sensitive information with consistent placeholders. Original files are NEVER modified. The redaction manifest documents every change for internal reference.

When to Use

  • Sharing documents with investors, advisors, or partners
  • Preparing materials for external review or cross-validation
  • Publishing case studies or documentation based on internal artifacts
  • Any situation where internal data must not leave the organization

When NOT to Use

  • Documents are already public — no redaction needed
  • User wants to delete files — that's not redaction
  • The sensitive data IS the deliverable (e.g., a security audit for the client)

Common Rationalizations

Thought Reality
"I'll just manually remove the sensitive parts" Manual redaction misses things. Automated scan + manifest catches more
"It's fine, the recipient is trusted" Trust the person, redact the document. People forward things
"I'll edit the originals and restore later" You won't. Original files must be untouched — copy first, always
"Only pricing needs redacting" Credentials, internal metrics, employee names, strategy details — audit first
"A quick find-and-replace is enough" Inconsistent placeholders leak information through correlation

Red Flags

  • Original files modified in place (SAFETY VIOLATION — must copy first)
  • Placeholder values are inconsistent (same entity gets different placeholders)
  • Grep after redaction still finds sensitive terms
  • Manifest is missing (no record of what was changed)
  • Redaction categories not defined before scanning (ad-hoc misses patterns)

SAFETY RULE

NEVER modify original files in place. All redaction happens on copies in .forge/redacted/. Original files in .forge/ must remain untouched. If you are about to edit a file outside .forge/redacted/, STOP.

Core Process

Read the full file on GitHub · 124 lines

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. 9d ago First seen · 124 lines · 63 tokens per session scan A f38f82c221d3

Subscribe to this mod's changes

redaction-and-cleanup is a skill published in the GitHub repository aneja5/forge-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 1,121 once invoked, about $0.0003 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-09-03.