agentmods.dev

op-clean

op-clean is a command for Claude Code from ogrodev/fsociety. It costs 12 tokens per session (689 once invoked), scanned A, original, MIT.

A command for removing logs, file metadata, and other forensic traces from a target system. Forensic traces are records that can help show what happened on a computer.

In plain words
What is it for?
Use only in an authorized environment for tasks such as a dry-run inventory or approved cleanup of logs and metadata. It supports scopes for logs, metadata, timestamps, or the full set.
Why use it?
It can erase evidence such as login records, system logs, file timestamps, and image or document metadata. Because these actions can destroy records and hide activity, they require careful authorization.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the trenton plugin — 5 skills, 12 commands, 2 agents shipped together

not rated 20repo 7mo ago A scan 12 tokens original MIT

Good fit Use only in an authorized environment for tasks such as a dry-run inventory or approved cleanup of logs and metadata. It supports scopes for logs, metadata, timestamps, or the full set.

Compare 6 commands from other repositories ↓
View source ↗ ogrodev/fsociety
Install

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.

Claude Code
/plugin marketplace add ogrodev/fsociety
Claude Code
/plugin install trenton

Made for: Claude Code.

Or install trenton, the plugin that ships this one along with the rest of its 5 skills, 12 commands, 2 agents.

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 op-clean

README.md
[![agentmods](https://agentmods.dev/badge/commands/ogrodev/fsociety/op-clean/github.svg)](https://agentmods.dev/commands/ogrodev/fsociety/op-clean)
Your own site
<a href="https://agentmods.dev/commands/ogrodev/fsociety/op-clean"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/op-clean/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 op-clean

Your own site · 80×15
<a href="https://agentmods.dev/commands/ogrodev/fsociety/op-clean"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/op-clean.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 689 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.00012 $0.00689
Opus 5.5 $0.00005 $0.00276
Sonnet 5.5 $0.00002 $0.00138
Haiku 4.5 $0.00001 $0.00069

Measured 2mo ago against content hash abed4c6a55ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

op-clean 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 2mo 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/commands/op-clean.md · 52 lines

What it actually says

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

Log and Trace Cleaning

Target and options: $ARGUMENTS

  1. Parse $ARGUMENTS for target host, --scope (default full), and --dry-run flag. Store parsed values for use throughout the command.

  2. If --dry-run is set: enumerate and list all artifacts that would be cleaned for each scope category without executing any destructive operations. Present a summary and exit.

  3. Logs (--scope logs or full): Clear system log entries:

    • Truncate or selectively edit /var/log/auth.log, /var/log/syslog, /var/log/kern.log
    • Run journalctl --vacuum-time=1s to purge systemd journal entries
    • Edit binary login records: wtmp (who was logged in), btmp (failed logins), lastlog (last login per user)
    • Clear application-specific logs as identified

  4. Metadata (--scope metadata or full): Strip file metadata from specified paths:

    • Use mat2 for broad metadata removal across file types
    • Use exiftool -all= for image and document EXIF/XMP data
    • Verify metadata removal by re-reading cleaned files

  5. Timestamps (--scope timestamps or full): Manipulate file timestamps to cover tracks:

    • Use touch -r <reference-file> <target-file> to copy timestamps from legitimate files
    • Use touch -t with specific timestamps to backdate modified files
    • Adjust directory timestamps to match surrounding entries

  6. Memory (--scope memory or full): Clear volatile forensic artifacts:

    • Clear swap: swapoff -a && swapon -a
    • Wipe bash/zsh/python history: truncate ~/.bash_history, ~/.zsh_history, ~/.python_history
    • Clear shared memory: remove contents of /dev/shm/
    • Drop page cache: echo 3 > /proc/sys/vm/drop_caches

  7. ALWAYS ask the user for explicit confirmation before executing any destructive operations via AskUserQuestion. Show exactly what will be modified or deleted.

  8. Log each cleaning action to the ops tracker with before/after state:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/ops-tracker.js" add <target> trace-clean <scope> "<action>" <before-state> <after-state>

  9. Write the cleaning report to the project directory. Include what was cleaned, what was skipped, and any artifacts that could not be removed.

  10. Update session metrics:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" metric traces_eliminated
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. 2mo ago First seen · 52 lines · 12 tokens per session scan A abed4c6a55ff

Subscribe to this mod's changes

op-clean is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 689 once invoked, about $0.0000 per session on Opus 5.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.

Claude CodeSecurityclaude-code-pluginoffensive-securitypentesting
Related

Other commands, from other repositories

pentest

Activate pentest mode — displays ASCII art, configures session isolation, collects engagement scope, then OWNS the engagement: pre-flight, recon, planning (via the pentester-orchestrator planner), executor dispatch, a time-budget quota loop, aggregation, and report generation.

Stickman230/claude-pentest · 58 tokens

pentest-scope

Define or update engagement scope — saves scope to disk without launching a pentest. Can be run before or during an engagement. If a pentest is active and the target changes drastically, warns the operator and suggests a new engagement.

Stickman230/claude-pentest · 51 tokens

pentest-attacks

Define the attack profile for an engagement — select which attack categories and skills to use. Saves to .pentest-attacks.json. If run before /pentest:pentest, the orchestrator will respect the selection. If run standalone, does not launch a pentest.

Stickman230/claude-pentest · 60 tokens

pentest-kali

Connect to a Metasploit-Kali Server (MKS) REST API — verifies connectivity, discovers available Kali tools, and configures agents to prefer MKS endpoints over local Bash equivalents.

Stickman230/claude-pentest · 43 tokens

pentest-exit

Close pentest session — summarizes findings, ensures outputs are saved, lifts isolation, and prompts for /clear.

Stickman230/claude-pentest · 26 tokens

bb-ad

Active Directory enumeration and attack techniques. Includes LDAP enumeration, Kerberos attacks (Kerberoasting, AS-REP Roasting), SMB attacks, and domain privilege escalation. Use this when targeting Windows domain environments.

allsmog/blackbox-claude-plugin · 44 tokens