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/analyze)<a href="https://agentmods.dev/commands/ogrodev/fsociety/analyze"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/analyze/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/analyze"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/analyze.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.00014 | $0.00909 |
| Opus 5.5 | $0.00006 | $0.00364 |
| Sonnet 5.5 | $0.00003 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
analyze 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.
How it starts
The opening of the file, as written. The whole thing — 109 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.
Full Binary Analysis
Parse $ARGUMENTS to get the binary path. This command runs the complete 8-phase reverse engineering workflow.
Pre-flight
- Verify the binary exists at the provided path.
- Check tool availability:
node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" check - If critical Tier 1 tools are missing, inform the user and suggest
/re-install.
Phase 1 — Initial Assessment
- Compute hashes:
node "${CLAUDE_PLUGIN_ROOT}/scripts/binary-hasher.js" hash "$ARGUMENTS" - Check for prior analysis:
node "${CLAUDE_PLUGIN_ROOT}/scripts/analysis-tracker.js" check "<sha256>" "full-analysis" - File type identification:
file <binary> - Record basic metadata: size, timestamps.
Phase 2 — PE Structure Analysis
Use radare2 for PE header analysis:
r2 -qc 'iH' <binary> # PE headers
r2 -qc 'iI' <binary> # Binary info
r2 -qc 'iS' <binary> # Sections (check entropy)
r2 -qc 'ii' <binary> # Imports
r2 -qc 'iE' <binary> # Exports
r2 -qc 'ir' <binary> # Resources
Flag suspicious indicators:
- High-entropy sections (>7.0 = likely packed)
- Unusual section names (.UPX, .aspack, .nsp)
- Suspicious imports (CreateRemoteThread, VirtualAllocEx, WSAStartup)
- TLS callbacks (anti-debug)
Phase 3 — String & Secret Extraction
strings -a -n 6 <binary> # ASCII strings
strings -a -n 6 -el <binary> # UTF-16 LE strings
floss <binary> # Obfuscated/stack strings
Regex-match for: URLs, IPs, emails, API keys (AWS AKIA*, Azure, GCP AIza*), JWT tokens (eyJ*), base64 blobs, file paths, registry keys, wallet addresses.
Log each finding:
node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" add "<binary>" "<type>" "<value>" "<severity>" "<title>"
Phase 4 — Disassembly & Function Analysis
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 · 109 lines · 14 tokens per session scan A 0d3d6f8f930b
analyze is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 909 once invoked, about $0.0001 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
ponytail-help
Quick reference for ponytail levels, skills, and commands.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
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.
agent-triage
Find and triage Quickchat conversations that need a human.