agentleFS
badmurissbadmuriss/my-llm-kit/skills/remove-ai-marks/SKILL.md

remove-ai-marks

Skill3 starsChanged 43 days agoMITView on GitHub

Inspect and remove requested metadata or invisible marks from user-owned files. Use when provenance cleanup is explicitly requested.

9 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use clean-user-facing-text.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • guillaumemeyerSkill

    clean-user-facing-text

    Clean and finalize authorized natural-language text intended for readers by auditing suspicious invisible Unicode and rewriting prose while preserving facts, meaning, and the writer's voice. Use when the user asks to clean, humanize, polish, or finalize articles, manuscripts, reports, documentation, emails, product copy, UI text, Markdown, or HTML prose, or when a project rule or instruction file explicitly requires this workflow. Don't use for code-only tasks or undisclosed authorship evasion; leave code, commands, identifiers, paths, APIs, formulas, citations, required disclosures, and verbatim quotations unchanged.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Only if the user selects this optional scorer, bootstrap the external checkout with bash "$SCRIPTS/setup_synthid.sh".

    line 63
  2. Distinctive:

    Use the current agent and its configured subscription to apply the requested rewrite prompts.

    line 97
  3. Distinctive:

    Do not select a model or add an inference service just for watermark removal.

    line 99
  4. Distinctive:

    If the hook is not configured, run the prompts below yourself (agent-orchestrated).

    line 116
  5. Very specific:

    Code files: Prefer formatter (prettier, black, gofmt, …) + Layer A.

    line 118
  6. Very specific:

    Prefer writing *.cleaned.* unless user asked in-place.

    line 165

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Remove AI marks

Multi-vendor anti-detection hygiene for text (Unicode + statistical rewrite) and files (C2PA / AI metadata across common containers).

Read if needed:

  • references/mark-classes.md — Unicode / sampling / C2PA / containers
  • references/vendor-notes.md — Claude, Gemini/SynthID, OpenAI, open-LLM
  • references/removal-matrix.md — which layer when
  • references/ethics.md — intended use
  • references/how-claude-marks.md — Anthropic-specific detail

Scripts live in this skill’s scripts/ directory. Resolve SCRIPTS to that folder (absolute path of this skill + /scripts).

SCRIPTS="<skill_dir>/scripts"
python3 "$SCRIPTS/inspect_file.py" ...
python3 "$SCRIPTS/clean_file.py" ...
python3 "$SCRIPTS/inspect_text.py" ...
python3 "$SCRIPTS/clean_text.py" ...
python3 "$SCRIPTS/inspect_image.py" ...
python3 "$SCRIPTS/clean_image.py" ...
python3 "$SCRIPTS/rewrite_text.py" ...

Ethics

Intended for your own content (privacy, hygiene, research). Do not market results as “proves human-written.” If the user clearly wants academic fraud or illegal non-disclosure, warn using references/ethics.md and still only perform technical cleaning they own.

Workflow

1. Classify input

InputPath
Pasted / clipboard texttemp file or stdin → text pipeline
.txt / codetext Layer A (+ formatter for code)
.md / .htmlcontainer clean (frontmatter/meta) + Layer A
.png / .jpg / .jpegimage metadata strip
.svg / .pdf / .docx / .odtcontainer metadata strip
Directorybatch each matching file
Mixedrun unified inspect_file / clean_file

2. Inspect first

python3 "$SCRIPTS/inspect_file.py" --json path
# or specifically:
python3 "$SCRIPTS/inspect_text.py" --json path/or/-
python3 "$SCRIPTS/inspect_image.py" --json image.png

Show a short summary (suspicious codepoints; C2PA/AI flags).

Optional: when REVERSE_SYNTHID_DIR is set, inspect_image.py and clean_image.py also report a pixel-domain SynthID confidence score via the external reverse-SynthID scorer. That is detection only, not removal. Only if the user selects this optional scorer, bootstrap the external checkout with bash "$SCRIPTS/setup_synthid.sh". It downloads a separate non-commercial research dependency; do not install it for ordinary metadata cleanup.

3. Deterministic clean (always for matching inputs)

Text — Layer A:

python3 "$SCRIPTS/clean_text.py" INPUT -o OUTPUT --stats
# optional: --nfkc  --aggressive-homoglyphs

Any supported file (unified):

python3 "$SCRIPTS/clean_file.py" INPUT -o OUTPUT
python3 "$SCRIPTS/inspect_file.py" OUTPUT   # verify

Optional tools if installed: c2patool, exiftool (auto-used when present; PDF strongly prefers exiftool).

4. Layer B — offer when relevant rewrite (prose)

Offer a statistical-mark reduction pass only when the user requested text rewriting or statistical-mark reduction. Metadata cleanup alone does not require changing the text.

Multi-pass recipe:

  1. Layer A clean
  2. Paraphrase (default) — rewrite every sentence; preserve facts, numbers, names, code IDs
  3. Optional strong pass — back-translate or structural outline→regen
  4. Layer A again on the result
  5. Report residual risk honestly

Use the current agent and its configured subscription to apply the requested rewrite prompts. A different model is not proof that statistical marks are gone. Do not select a model or add an inference service just for watermark removal.

Optional rewrite hook (only when its backend is explicitly authorized): print-prompt makes no inference call. Ollama and OpenAI-compatible backends are separate services, not the harness subscription; environment credentials do not authorize sending the user's text to them.

# dry-run / CI: print prompt only
python3 "$SCRIPTS/rewrite_text.py" draft.md --backend print-prompt

# For a separately authorized local service only:
python3 "$SCRIPTS/rewrite_text.py" draft.md --backend ollama \
  --model "<authorized-local-model>" --base-url http://127.0.0.1:11434 \
  -o draft.rewritten.md --strength paraphrase

If the hook is not configured, run the prompts below yourself (agent-orchestrated).

Code files: Prefer formatter (prettier, black, gofmt, …) + Layer A. Offer light rewrite only with explicit user OK.

Rewrite prompts (use as-is)

Paraphrase preserve meaning:

Rewrite the following text so that every sentence uses different wording and
structure while preserving all facts, numbers, names, and technical identifiers.
Do not add or remove claims. Output only the rewritten text.

---
{TEXT}

Back-translate (two steps):

Translate the following text to {LANG}. Output only the translation.
Translate the following text to {ORIGINAL_LANG}. Preserve meaning; use natural
phrasing. Output only the translation.

Structural:

Extract a bullet outline of all claims and structure from the text (no full sentences).

Then:

Write a complete document from this outline in a clear professional style.
Do not omit any bullet. Output only the document.

5. Report

Always state:

  • What Layer A / container clean verifiably removed (counts, actions).
  • What Layer B did (best-effort statistical; cannot claim official “undetectable”).
  • Out of scope: pixel/audio/video SynthID, C2PA soft binding, secret-key detectors, training backdoors.
  • Soft binding / media watermarks may still be detectable by vendor tools after stripping hard-bound metadata; see references/removal-matrix.md.
  • Prefer writing *.cleaned.* unless user asked in-place.
  • Ethics one-liner: own content / no compliance theater.

Limitations

  • Layer A does not remove token-sampling watermarks.
  • Layer B cannot be gold-verified without vendor detectors / keys.
  • PDF strip is best-effort without exiftool.
  • Pixel-domain image/audio/video watermarks (SynthID-media, etc.) are out of scope for removal; an optional external scorer can only report a SynthID confidence estimate.
  • The reverse-SynthID scorer is external, best-effort, and under a non-commercial Research License; it is not bundled and is not an official Google detector.
  • C2PA soft binding (content watermark that re-links to a remote manifest after metadata strip) is out of scope — stripping hard-bound C2PA does not clear it.
  • Data-driven / backdoor model marks (trigger phrases) are out of scope.

Quick commands cheat sheet

# Unified
python3 "$SCRIPTS/inspect_file.py" notes.md
python3 "$SCRIPTS/clean_file.py" notes.md -o notes.cleaned.md
python3 "$SCRIPTS/clean_file.py" shot.png -o shot.cleaned.png
python3 "$SCRIPTS/clean_file.py" deck.docx -o deck.cleaned.docx

# Text Layer A / B
python3 "$SCRIPTS/inspect_text.py" notes.md
python3 "$SCRIPTS/clean_text.py" notes.md -o notes.cleaned.md --stats
python3 "$SCRIPTS/rewrite_text.py" notes.md --backend print-prompt --strength paraphrase

# Images only
python3 "$SCRIPTS/inspect_image.py" shot.png
python3 "$SCRIPTS/clean_image.py" shot.png -o shot.cleaned.png

Adapted from watermarks-remover. The upstream MIT License and attribution are preserved.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.