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.
npx agentmods add commands/ogrodev/fsociety/op-wipegit clone --depth 1 https://github.com/ogrodev/fsocietyWrote 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/ogrodev/fsociety/op-wipe)<a href="https://agentmods.dev/commands/ogrodev/fsociety/op-wipe"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/op-wipe.svg" alt="Measured on agentmods" 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 | $0.00014 | $0.00499 |
| Opus 5 | $0.00007 | $0.00249 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade C, and why
op-wipe scanned grade C with 1 finding 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 today.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
4. **For directories**: Recursively wipe all file contents within the directory first (applying the selected method to each file), then remove the empty directory structure with `rm -rf`. 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.
Secure File Wipe
Target and options: $ARGUMENTS
-
Parse
$ARGUMENTSfor target path,--passes(default3), and--method(defaultshred). Validate that the target path exists and is accessible. -
ALWAYS ask the user for explicit confirmation before wiping via
AskUserQuestion. Display the exact paths that will be destroyed, the number of passes, and the method. Make clear this operation is irreversible. -
For files: Execute the secure wipe using the selected method:
shred:shred -vfz -n <passes> <file>— overwrite with random data, then zero-fill final passsrm:srm -z <file>— secure remove with zero-filldd:dd if=/dev/urandom of=<file> bs=4096 count=<filesize/4096> conv=notrunc && sync && rm <file>— overwrite with urandom then delete
-
For directories: Recursively wipe all file contents within the directory first (applying the selected method to each file), then remove the empty directory structure with
rm -rf. -
For free space: Fill remaining free space on the mount point with random data, sync, then remove:
dd if=/dev/urandom of=<mount>/wipefile bs=1M sync rm <mount>/wipefile -
Log the wipe operation to the ops tracker:
node "${CLAUDE_PLUGIN_ROOT}/scripts/ops-tracker.js" add <target> secure-wipe <method> "<path>" <passes> <result> -
Verify the file or directory is completely gone. Attempt to read the path and confirm it no longer exists. For free space wipes, confirm the wipefile was removed.
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.
- today First seen · 37 lines · 14 tokens per session scan C 3652a59f371a
op-wipe is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 499 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
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.
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.
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.
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.
pentest-exit
Close pentest session — summarizes findings, ensures outputs are saved, lifts isolation, and prompts for /clear.
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.