agentmods.dev

op-campaign

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

An operations-security campaign runner with saved progress between steps. Operations security, or opsec, means reducing the chance that sensitive systems, actions, or information are exposed.

In plain words
What is it for?
Use it to check status, resume work, dispatch the next delegated step, record notes, or mark a phase complete.
Why use it?
It helps continue a multi-step security campaign without losing track of the current phase or repeating completed work.

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 10 tokens original 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-campaign
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-campaign

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

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00453
Opus 5 $0.00005 $0.00227
Sonnet 5 $0.00002 $0.00091
Haiku 4.5 $0.00001 $0.00045

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

Security

Grade A, and why

op-campaign 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 4d 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.

trenton/commands/op-campaign.md · 38 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.

Campaign Runner

Subcommand: $ARGUMENTS

Orchestrator Rules (YOU must follow these)

  • YOU are the orchestrator. YOU stay at <30% context usage
  • Each executor subagent gets 100% fresh context via Task tool
  • NEVER run offensive tools yourself — ALWAYS delegate to subagent executors

Dispatch

  • status: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show
  • resume: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" smart-resume and act on recommendation
  • next: Spawn fresh Task subagent executor for the next step. Pass full context: operation, target, current phase, step number, tool instructions, output format requirements
  • complete-step: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" complete-step --summary "<summary>"
  • complete-phase: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" complete-phase --summary "<summary>"
  • reset: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" reset
  • note : node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" add-note "<text>"

Executor Subagent Template

When spawning a Task executor for "next", include:

  1. Operation name and target
  2. Current phase and step details
  3. Exact tools to use and in what order
  4. Expected output format: RESULT, OPS_COUNT, SUMMARY, ALERTS, NEXT_RECOMMENDATION
  5. Storage policy reminder
  6. Script paths for logging results

After Each Step

Collect executor's output. Parse results. Update state. Ask user to continue or adjust.

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. 4d ago First seen · 38 lines · 10 tokens per session scan A f9dce20cd96b

Subscribe to this mod's changes

op-campaign is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 453 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-08-30.

Marketing and SEOSecurityclaude-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