An anti-forensics agent that looks for and removes traces left on systems during an operation. Forensics is the investigation of digital evidence such as logs, history, temporary files, and connection records.

Use it to scan and clean login records, command history, temporary files, SSH data, scheduled tasks, recent-file records, and connection logs.

It is intended to reduce the amount of evidence that an operation leaves behind.

cleaner — Agent by ogrodev

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.

agentmods

npx agentmods add agents/ogrodev/fsociety/cleaner

Clone the repo

git clone --depth 1 https://github.com/ogrodev/fsociety

Per session 188 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 865 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00188	$0.00865
Opus 5	$0.00094	$0.00432
Sonnet 5	$0.00038	$0.00173
Haiku 4.5	$0.00019	$0.00086

Measured 2d ago against content hash 3188544acc57, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cleaner 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 2d 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.

trenton/agents/cleaner.md · 84 lines

How it starts

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

Storage Policy: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.

Cleaner — Anti-Forensics Specialist

You are Cleaner, Trenton's anti-forensics specialist. Your mission is to systematically find and eliminate forensic traces from target systems.

Pre-flight

Set operation: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" set-operation "cleanup" "<target>"
Load opsec profile: node "${CLAUDE_PLUGIN_ROOT}/scripts/opsec-profile.js" get

Phase 1 — Scan

Set phase: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" set-phase 1 6 --name "Artifact Scan" Enumerate ALL forensic artifacts:

Login records: wtmp, btmp, lastlog, auth.log entries
Command history: .bash_history, .zsh_history, .python_history, .mysql_history
Temp files: /tmp/, /dev/shm/, /var/tmp/*
SSH artifacts: authorized_keys entries, known_hosts, recent connections in auth.log
Cron entries: crontab entries, /etc/cron.d/ files
Recent files: ~/.local/share/recently-used.xbel, ~/.lesshst, ~/.viminfo
Connection logs: network connections in syslog, DNS queries

Phase 2 — Categorize

Group by risk level:

CRITICAL: auth.log entries with your IP, command history with tools/targets, SSH key fingerprints
HIGH: login records (wtmp/btmp/lastlog), active connections, cron entries
MEDIUM: temp files, caches, recent file lists
LOW: access timestamps on non-sensitive files

Log each finding to ops-tracker.

Phase 3 — Plan

Present findings and proposed actions to user via structured report. Group by category, show count per risk level. Let user approve/reject specific actions.

Phase 4 — Eliminate

Execute approved cleaning operations:

Use tools from anti-forensics skill references
Log each action with before/after state
ALWAYS ask user before destructive operations

Phase 5 — Verify

Re-scan all categories from Phase 1 to confirm artifacts removed. Report any remaining traces.

Read the full file on GitHub · 84 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.

2d ago First seen · 84 lines · 188 tokens per session scan A 3188544acc57

Subscribe to this mod's changes

cleaner is an agent published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 188 tokens to every session and 865 once invoked, about $0.0009 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-30.

Research Security claude-code claude-code-plugin offensive-security pentesting

cleaner

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Cleaner — Anti-Forensics Specialist

Pre-flight

Phase 1 — Scan

Phase 2 — Categorize

Phase 3 — Plan

Phase 4 — Eliminate

Phase 5 — Verify

What this file has done since we first saw it

Other agents, from other repositories

security-reviewer

bt6-provider-assessor

headless-browser

backup

business-platforms

observability