ty-campaign

ty-campaign is a command for Claude Code from ogrodev/fsociety. It costs 10 tokens per session (931 once invoked), scanned A, original, MIT.

A campaign manager for coordinating searches for leaked data and recording progress between steps.

In plain words
What is it for?
Resuming campaigns, assigning search tasks to separate agents, and recording findings, decisions, and blockers.
Why use it?
It keeps a multi-step leak investigation organized and lets work resume from saved state.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the tyrell plugin — 5 skills, 16 commands, 2 agents shipped together

Good fit Resuming campaigns, assigning search tasks to separate agents, and recording findings, decisions, and blockers.

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add ogrodev/fsociety
Claude Code
/plugin install tyrell

Made for: Claude Code.

Or install tyrell, the plugin that ships this one along with the rest of its 5 skills, 16 commands, 2 agents.

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 ty-campaign

README.md
[![agentmods](https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-campaign/github.svg)](https://agentmods.dev/commands/ogrodev/fsociety/ty-campaign)
Your own site
<a href="https://agentmods.dev/commands/ogrodev/fsociety/ty-campaign"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-campaign/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.

agentmods 80×15 button for ty-campaign

Your own site · 80×15
<a href="https://agentmods.dev/commands/ogrodev/fsociety/ty-campaign"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-campaign.svg" alt="Reviewed on agentmods" width="80" 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 931 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00010 $0.00931
Opus 5.5 $0.00004 $0.00372
Sonnet 5.5 $0.00002 $0.00186
Haiku 4.5 $0.00001 $0.00093

Measured 2mo ago against content hash 12edfb556f63, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ty-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 2mo 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.

tyrell/commands/ty-campaign.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Storage Policy: ALL output files MUST be saved in the project directory. NEVER write to /tmp/ or any system temporary directory.

Hunt Campaign Runner (Orchestrator)

You are a lean orchestrator. Read state, determine the next action, spawn fresh executor subagents for heavy work, and update state with results.

Context budget: YOU stay under 30%. Each executor gets 100% fresh.

The user's argument: $ARGUMENTS


State Tool Reference

All state commands: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" <command>

Key commands:

  • show — full state
  • smart-resume — JSON next-action analysis
  • set-step <n> [total] --action "<desc>" — set current step
  • complete-step --summary "<text>" --result "<type>" --findings <n>
  • complete-phase --summary "<text>"
  • track-agent <id> <type> <task> / complete-agent <id> --result "<text>"
  • add-note <text> / add-decision <text> / add-blocker <text>
  • metric <key> +1

Dispatch

status or no arguments

node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show

resume

  1. Run: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" smart-resume
  2. Parse JSON. Check .continue-here.md.
  3. Present highest-priority action and ask to proceed.
  4. Delete .continue-here.md after resuming.

next

Execute next step via executor subagent pattern:

  1. Read plan file (Glob plan-*.md, PLAN.md)
  2. Get state: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show
  3. Check for duplicates: node "${CLAUDE_PLUGIN_ROOT}/scripts/source-tracker.js" search "<keywords>"
  4. Set step: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" set-step <n> <total> --action "<desc>"
  5. Track agent: node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" track-agent "<id>" "executor" "<task>"
  6. Spawn fresh Task subagent with step context
  7. Collect results, complete agent, complete step, update metrics
  8. Check for pivots
  9. Report and ask: continue or pause?

Read the full file on GitHub · 112 lines

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. 2mo ago First seen · 112 lines · 10 tokens per session scan A 12edfb556f63

Subscribe to this mod's changes

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