agentmods.dev

op-planner

op-planner is a command for coding agents from ogrodev/fsociety. It costs 14 tokens per session (404 once invoked), scanned A, original, MIT.

Analyze current opsec posture and create a strategic hardening/cleanup plan.

Command

Installs and runs on its own, but its text points at files inside the plugin that ships it — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed.

not rated 20 5mo ago A scan 14 tokens MIT
View the source file ogrodev/fsociety
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/op-planner
Clone the repo
git clone --depth 1 https://github.com/ogrodev/fsociety

Wrote 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.

agentmods badge for op-planner

README.md
[![agentmods](https://agentmods.dev/badge/commands/ogrodev/fsociety/op-planner.svg)](https://agentmods.dev/commands/ogrodev/fsociety/op-planner)
Your own site
<a href="https://agentmods.dev/commands/ogrodev/fsociety/op-planner"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/op-planner.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 404 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00014 $0.00404
Opus 5 $0.00007 $0.00202
Sonnet 5 $0.00003 $0.00081
Haiku 4.5 $0.00001 $0.00040

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

Security

Grade A, and why

op-planner 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 today.

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.

trenton/commands/op-planner.md · 40 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.

Strategic Opsec Planning

Focus area: $ARGUMENTS

Phase 1: Gather Current State

  1. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/ops-tracker.js" summary and coverage
  2. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/identity-tracker.js" summary
  3. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/opsec-profile.js" show
  4. Run node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show

Phase 2: Analyze Gaps

Build two maps:

  • Battle Scars: What has already been checked/hardened/cleaned
  • Blind Spots: Categories with no operations, unchecked areas

Phase 3: Propose Campaigns

Identify 3-5 campaign options based on gaps. Examples:

  • "Full VPS Hardening" — kernel, SSH, firewall, services, monitoring
  • "Trace Elimination" — logs, metadata, timestamps, memory, history
  • "Anonymous Infrastructure" — proxy chains, VPN killswitch, identity rotation, DNS protection
  • "Complete Identity Reset" — MAC, hostname, DNS, Tor circuit, VPN endpoint

Phase 4: Present to User

Use AskUserQuestion to let user pick campaign(s).

Phase 5: Create Plan

Use EnterPlanMode. Write detailed step-by-step plan.

Phase 6: Initialize Campaign

Set operation: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" set-operation "<campaign-name>" "<target>" Set phases.

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.

  1. today First seen · 40 lines · 14 tokens per session scan A c6ae161570f7

Subscribe to this mod's changes

op-planner is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 404 once invoked, about $0.0001 per session on Opus 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-09-03.

PlanningSecurityclaude-codeclaude-code-pluginoffensive-securitypentesting
Related

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.

Stickman230/claude-pentest · 58 tokens

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.

Stickman230/claude-pentest · 60 tokens

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.

Stickman230/claude-pentest · 43 tokens

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.

Stickman230/claude-pentest · 51 tokens

pentest-exit

Close pentest session — summarizes findings, ensures outputs are saved, lifts isolation, and prompts for /clear.

Stickman230/claude-pentest · 26 tokens

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.

allsmog/blackbox-claude-plugin · 44 tokens