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.
/plugin marketplace add ogrodev/fsociety/plugin install romeroWrote 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/diff)<a href="https://agentmods.dev/commands/ogrodev/fsociety/diff"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/diff/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.
<a href="https://agentmods.dev/commands/ogrodev/fsociety/diff"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/diff.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00010 | $0.00487 |
| Opus 5.5 | $0.00004 | $0.00195 |
| Sonnet 5.5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
diff 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 1mo 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.
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.
Binary Diffing
Parse $ARGUMENTS for two binary paths (space-separated).
Step 1 — Hash Both Binaries
node "${CLAUDE_PLUGIN_ROOT}/scripts/binary-hasher.js" hash "<binary1>"
node "${CLAUDE_PLUGIN_ROOT}/scripts/binary-hasher.js" hash "<binary2>"
If hashes are identical, report "Binaries are identical" and exit.
Step 2 — File Size Comparison
Compare file sizes and report delta.
Step 3 — Byte-Level Diff
radiff2 <binary1> <binary2>
This shows byte-level differences between the two files.
Step 4 — Section Comparison
r2 -qc 'iS' <binary1>
r2 -qc 'iS' <binary2>
Compare section names, sizes, entropy, and virtual addresses.
Step 5 — Import/Export Diff
r2 -qc 'ii' <binary1> > imports1.txt
r2 -qc 'ii' <binary2> > imports2.txt
diff imports1.txt imports2.txt
Compare new imports, removed imports, and changed ordinals.
Step 6 — Function-Level Diff
r2 -qc 'aaa; afl' <binary1>
r2 -qc 'aaa; afl' <binary2>
Compare function lists: new functions, removed functions, changed sizes.
Step 7 — ssdeep Similarity
ssdeep <binary1> <binary2>
Report similarity percentage.
Step 8 — Report
Save report to diff-<name1>-vs-<name2>.md with sections:
- File Identification (both binaries)
- Size Delta
- Section Differences
- Import/Export Changes
- Function Changes
- ssdeep Similarity Score
- Security-Relevant Changes (if any)
- Recommendations
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.
- 1mo ago First seen · 81 lines · 10 tokens per session scan A 435d7bdbefb8
diff is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 487 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.
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-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-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-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.