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.
/plugin marketplace add ogrodev/fsociety/plugin install tyrellWrote 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.
[](https://agentmods.dev/commands/ogrodev/fsociety/ty-campaign)<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.
<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>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.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 |
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.
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 statesmart-resume— JSON next-action analysisset-step <n> [total] --action "<desc>"— set current stepcomplete-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
- Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" smart-resume - Parse JSON. Check
.continue-here.md. - Present highest-priority action and ask to proceed.
- Delete
.continue-here.mdafter resuming.
next
Execute next step via executor subagent pattern:
- Read plan file (Glob
plan-*.md,PLAN.md) - Get state:
node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show - Check for duplicates:
node "${CLAUDE_PLUGIN_ROOT}/scripts/source-tracker.js" search "<keywords>" - Set step:
node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" set-step <n> <total> --action "<desc>" - Track agent:
node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" track-agent "<id>" "executor" "<task>" - Spawn fresh Task subagent with step context
- Collect results, complete agent, complete step, update metrics
- Check for pivots
- Report and ask: continue or pause?
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.
- 2mo ago First seen · 112 lines · 10 tokens per session scan A 12edfb556f63
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.
Other commands, from other repositories
octo-schedule
Manage scheduled workflow jobs for the Claude Octopus scheduler.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
next
Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…
prd-score
Score an existing PRD against the 100-point AI-optimization framework.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
feat
Kick off tasks creation for a new feature (4-item interview before invoking pm-agent; an epic-sized requirement routes to phased decomposition, a feature already built on one platform routes to cross-platform parity, a change that touches no endpoint routes to client-only).