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.
npx agentmods add commands/ogrodev/fsociety/ty-handoffgit clone --depth 1 https://github.com/ogrodev/fsocietyWrote 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-handoff)<a href="https://agentmods.dev/commands/ogrodev/fsociety/ty-handoff"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-handoff.svg" alt="Measured on agentmods" 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 | $0.00012 | $0.01002 |
| Opus 5 | $0.00006 | $0.00501 |
| Sonnet 5 | $0.00002 | $0.00200 |
| Haiku 4.5 | $0.00001 | $0.00100 |
Grade A, and why
ty-handoff 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are generating an elliot handoff package for the tyrell data exfiltration plugin.
Step 1 — Retrieve Source and Acquisition Records
Pull the full source record and any associated acquisition data:
node "${CLAUDE_PLUGIN_ROOT}/scripts/source-tracker.js" list --id $ARGUMENTS
node "${CLAUDE_PLUGIN_ROOT}/scripts/acquisition-tracker.js" list --source-id $ARGUMENTS
Confirm the source has been acquired before generating a handoff. If no acquisition record exists, recommend running /ty-acquire <source-id> first.
Step 2 — Build the Handoff Package
Run the handoff builder with all available context:
node "${CLAUDE_PLUGIN_ROOT}/scripts/handoff-builder.js" create $ARGUMENTS
The handoff builder will:
- Read the source and acquisition records
- Extract schema and field mapping from the dump
- Identify credential pairs (username, password, hash) for credential stuffing
- Identify session tokens, API keys, or access tokens in the data
- Map discovered credentials against the target's known tech stack
- Produce a structured handoff package in
${CLAUDE_PLUGIN_ROOT}/data/handoffs/<source-id>/
Step 3 — Enrich with Tech Stack and Defense Context
If --tech-stack or --defenses were provided in $ARGUMENTS, or if known from the source context, append this intelligence to the handoff:
node "${CLAUDE_PLUGIN_ROOT}/scripts/handoff-builder.js" enrich \
--source-id "<source-id>" \
--tech-stack "<tech-stack-value>" \
--defenses "<defenses-value>"
Tech stack context guides elliot on which exploitation paths to prioritize (e.g., discovered MySQL credentials mapped against a WordPress target suggest wp-login credential stuffing before direct DB access).
Defense context guides elliot on evasion requirements (e.g., WAF present, rate limiting, MFA on admin panels).
Step 4 — Generate Handoff Report
The handoff package is written to disk. Display its contents summary:
node "${CLAUDE_PLUGIN_ROOT}/scripts/handoff-builder.js" summary \
--source-id "<source-id>"
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.
- today First seen · 115 lines · 12 tokens per session scan A a8e8f5abc0fb
ty-handoff is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 1,002 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.
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-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-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-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.