apiscan
API security audit — REST, GraphQL, JWT analysis, parameter discovery
Check and install opsec tools — verify availability or auto-install missing dependencies
> /plugin marketplace add ogrodev/fsociety > /plugin install fsociety@ogrodev-fsociety
How it fires
How this command gets triggered: by you, by Claude, or both.
/op-installContext preview
What this command does when you run it.
Check and install opsec tools — verify availability or auto-install missing dependencies
description: Check and install opsec tools — verify availability or auto-install missing dependencies allowed-tools: Bash, Read, Write, AskUserQuestion argument-hint: [--auto | --check-only | <tool-name>]
> **Storage Policy**: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.
1. Parse `$ARGUMENTS` for flags (`--auto`, `--check-only`, or a specific tool name) 2. If `--check-only` or no args: run `node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" check` to list all tools and their availability 3. If a specific tool name is provided: run `node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" check <tool>` to check that single tool 4. If `--auto`: run `node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" install-missing` to install all missing tools 5. Otherwise, show the list of missing tools and ask the user which to install via AskUserQuestion 6. Always ask user approval before running any install commands 7. After installation, run `node "${CLAUDE_PLUGIN_ROOT}/scripts/tool-checker.js" check` to verify tools were installed successfully
Multi-plugin marketplace for Claude Code offensive security plugins
Repo: ogrodev/fsociety
API security audit — REST, GraphQL, JWT analysis, parameter discovery
Archive or list previous engagement snapshots
Password brute force and hash cracking against target services
Resume or execute an attack campaign with progress tracking
Show running scans, system health, and engagement status