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 elliotWrote 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/timeline)<a href="https://agentmods.dev/commands/ogrodev/fsociety/timeline"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/timeline/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/timeline"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/timeline.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.00545 |
| Opus 5.5 | $0.00004 | $0.00218 |
| Sonnet 5.5 | $0.00002 | $0.00109 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
timeline 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.
What it actually says
Engagement Timeline
Build a chronological view of the entire engagement by merging all event sources.
The user's argument: $ARGUMENTS
Gather Events
Read these data sources:
1. Findings
node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list
Each finding has a first_seen date. Parse the output or read findings-db.jsonl directly for timestamps.
2. Techniques
node "${CLAUDE_PLUGIN_ROOT}/scripts/techniques-tracker.js" list
Each technique has a timestamp field. Parse the output or read techniques-db.jsonl directly.
3. Session State
node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" show
Extract decisions (have timestamps), blockers, notes, phase completions, and agent history.
Merge & Sort
Combine all events into a single timeline. Each event gets:
- Timestamp (ISO or date)
- Type icon:
[F]finding,[T]technique,[D]decision,[B]blocker,[N]note,[A]agent,[P]phase - Description: One-line summary
Sort by timestamp, most recent first (reverse-chrono).
If --last N is specified, show only the last N events.
Format Output
Group by date, reverse-chrono:
=== 2025-01-15 ===
14:32 [F] CRITICAL — SQL Injection in /api/users (f-012)
14:30 [T] sqlmap on target.com → success
13:15 [D] Pivoted to database testing after SQLi discovery
12:00 [T] nuclei on target.com → partial
11:45 [P] Phase 2 completed — 4 findings
=== 2025-01-14 ===
16:20 [F] HIGH — IDOR in /api/payments (f-008)
15:00 [B] Rate limit detected on /api/auth
14:00 [T] dalfox on target.com → clean
10:30 [N] Started API testing campaign
Keep it concise. One line per event. No raw data dumps.
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 · 66 lines · 10 tokens per session scan A 35c6ec864880
timeline 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 545 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-08-30.
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.