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/secrets)<a href="https://agentmods.dev/commands/ogrodev/fsociety/secrets"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/secrets/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/secrets"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/secrets.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.00008 | $0.00750 |
| Opus 5.5 | $0.00003 | $0.00300 |
| Sonnet 5.5 | $0.00002 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
secrets 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 — 80 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.
Secret & Credential Extraction
Parse $ARGUMENTS to get the binary path.
Step 1 — Hash & Validate
node "${CLAUDE_PLUGIN_ROOT}/scripts/binary-hasher.js" hash "$ARGUMENTS"
Step 2 — String Extraction
Run both ASCII and Unicode extraction:
strings -a -n 6 <binary> # ASCII strings (min 6 chars)
strings -a -n 6 -el <binary> # UTF-16 LE strings
Step 3 — Obfuscated Strings
floss <binary> # FLARE Obfuscated String Solver
FLOSS will extract stack strings, tight strings, and decoded strings that strings misses.
Step 4 — Pattern Matching
Apply regex patterns to all extracted strings:
| Pattern | Type | Example |
|---|---|---|
https?://[^\s"']+ |
url | http://c2.evil.com/beacon |
\d{1,3}\.\d{1,3}\.\d{1,3}\.\d{1,3} |
ip | 192.168.1.100 |
AKIA[0-9A-Z]{16} |
api-key | AWS Access Key |
AIza[0-9A-Za-z_-]{35} |
api-key | GCP API Key |
eyJ[A-Za-z0-9_-]+\.eyJ[A-Za-z0-9_-]+ |
token | JWT Token |
[a-zA-Z0-9+/]{40,}={0,2} |
credential | Base64 encoded blob |
-----BEGIN .* KEY----- |
crypto-key | PEM private key |
HKEY_(LOCAL_MACHINE|CURRENT_USER)\\.* |
registry-key | Registry path |
[13][a-km-zA-HJ-NP-Z1-9]{25,34} |
wallet | Bitcoin address |
password\s*[=:]\s*\S+ |
credential | Hardcoded password |
(user|admin|login)\s*[=:]\s*\S+ |
credential | Username/credential |
Data Source=.* |
credential | Connection string |
Step 5 — Base64 Decode
For each base64 blob found, decode and inspect:
echo "<blob>" | base64 -d 2>/dev/null
Look for decoded URLs, commands, scripts, or binary data.
Step 6 — Log Findings
For each unique finding:
node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" add "<binary>" "<type>" "<value>" "<severity>" "<title>"
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 · 80 lines · 8 tokens per session scan A 42d7e5f230a8
secrets is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 8 tokens to every session and 750 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.