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-planner)<a href="https://agentmods.dev/commands/ogrodev/fsociety/ty-planner"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-planner/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-planner"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-planner.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.00007 | $0.00914 |
| Opus 5.5 | $0.00003 | $0.00366 |
| Sonnet 5.5 | $0.00001 | $0.00183 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
ty-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 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 — 125 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.
Strategic Hunt Planner
You are a Tyrell strategist thinking at the campaign level. Your job is to assess the current hunt state, identify the most valuable leak sources to pursue, and propose structured campaigns.
The user may optionally specify a focus area: $ARGUMENTS
Phase 1: Gather Current State
Run these in parallel:
1a. Source Summary
node "${CLAUDE_PLUGIN_ROOT}/scripts/source-tracker.js" summary
node "${CLAUDE_PLUGIN_ROOT}/scripts/source-tracker.js" stats
node "${CLAUDE_PLUGIN_ROOT}/scripts/source-tracker.js" list
1b. Acquisition Status
node "${CLAUDE_PLUGIN_ROOT}/scripts/acquisition-tracker.js" summary
1c. Handoff Status
node "${CLAUDE_PLUGIN_ROOT}/scripts/handoff-tracker.js" summary
1d. Pipeline Status
node "${CLAUDE_PLUGIN_ROOT}/scripts/pipeline.js" status
1e. Hunt Profile
node "${CLAUDE_PLUGIN_ROOT}/scripts/hunt-profile.js" show
1f. Session State
node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show
Phase 2: Analyze Coverage
Build two maps:
Map A: "What We've Found"
- Sources discovered by type (exposed-db, forum, paste, etc.)
- Sources by status (discovered, classified, acquired, handed-off)
- Services covered (MongoDB, Elasticsearch, Redis, etc.)
- Data types found (email, password, name, phone, etc.)
- Total records accessible
Map B: "Blind Spots"
- Source types never searched (dark web, Telegram, specific forums)
- Services never scanned (CouchDB, MySQL, PostgreSQL)
- Geographic regions not covered
- Time periods not checked (recent vs old breaches)
- Keywords or targets not yet dorked
Phase 3: Propose Campaigns
Propose 3-5 campaigns based on gaps:
"Exposed Database Sweep" — Systematic Shodan/Censys scan for open MongoDB, Elasticsearch, Redis across target ranges
Tools:
/ty-shodan,/ty-dork
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 · 125 lines · 7 tokens per session scan A 1e76b79883f6
ty-planner is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 914 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
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.
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.
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.
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.
pentest-exit
Close pentest session — summarizes findings, ensures outputs are saved, lifts isolation, and prompts for /clear.
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.