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/re-install)<a href="https://agentmods.dev/commands/ogrodev/fsociety/re-install"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/re-install/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/re-install"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/re-install.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.00009 | $0.00493 |
| Opus 5.5 | $0.00004 | $0.00197 |
| Sonnet 5.5 | $0.00002 | $0.00099 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade B, and why
re-install scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt install -y <packages> 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.
RE Tool Installer
Parse $ARGUMENTS for flags:
--check-only— Display installed/missing tools, do not install--auto— Install all missing tools (with user confirmation)<tool-name>— Install a specific tool- (no args) — Interactive mode: show status, ask what to install
Step 1 — Check Tool Status
node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" check
Step 2 — Handle Flags
If --check-only: Display the tool status table and exit.
If --auto:
node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" install-missing
Show the install commands and ask the user for confirmation before running them.
If <tool-name>:
node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" check <tool-name>
If not installed, show the install command and ask for confirmation.
If no args (interactive):
- Show the tool status table.
- If any Tier 1 tools are missing, ask:
AskUserQuestion: Critical RE tools are missing. What would you like to do? 1. Install all missing Tier 1 tools (recommended) 2. Install all missing tools (Tier 1-3) 3. Choose specific tools to install 4. Skip for now - Execute based on user choice.
Step 3 — Execute Installation
ALWAYS ask for user approval before running any apt install or pip install command.
Run installation commands:
sudo apt install -y <packages>
pip install <packages>
Step 4 — Verify
After installation, re-run the check:
node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" check
Report success/failure for each tool.
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 · 69 lines · 9 tokens per session scan B d774a753ecf1
re-install is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 493 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). 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.