A command workflow for checking and installing reverse-engineering tools on Kali Linux, a Linux distribution often used for security testing.

Use it to check all tools, check one named tool, install missing tools automatically after confirmation, or handle installation interactively while keeping output in the project directory.

It shows which tools are missing and requires confirmation before installation commands are run.

re-install — Command by ogrodev

Install

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.

agentmods

npx agentmods add commands/ogrodev/fsociety/re-install

Clone the repo

git clone --depth 1 https://github.com/ogrodev/fsociety

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 493 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00009	$0.00493
Opus 5	$0.00005	$0.00246
Sonnet 5	$0.00002	$0.00099
Haiku 4.5	$0.00001	$0.00049

Measured 2d ago against content hash d774a753ecf1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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>

romero/commands/re-install.md · 69 lines

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.

Changes

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.

2d ago First seen · 69 lines · 9 tokens per session scan B d774a753ecf1

Subscribe to this mod's changes

re-install is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 493 once invoked, about $0.0000 per session on Opus 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.

Productivity Security Testing claude-code claude-code-plugin offensive-security pentesting

pr

Create a PR to main branch using conventional commit style for the title.

KeygraphHQ/shannon · 13 tokens

engage.scope

Execute Phase 0 - Scope Definition and Rules of Engagement.

hypnguyen1209/offensive-claude · 11 tokens

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.

Stickman230/claude-pentest · 58 tokens

re-install