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.
git 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/dashboard)<a href="https://agentmods.dev/commands/ogrodev/fsociety/dashboard"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/dashboard/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/dashboard"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/dashboard.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.00349 |
| Opus 5.5 | $0.00004 | $0.00140 |
| Sonnet 5.5 | $0.00002 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
dashboard 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 Dashboard
Display current engagement status, running processes, and system health.
Step 1: Load Tools
Use ToolSearch to load:
get_live_dashboard— live dashboard with process monitoringlist_active_processes— show all active Hexstrike processesdisplay_system_metrics— system resource usageget_cache_stats— tool cache statisticsserver_health— Hexstrike server health check
Step 2: Server Health
Run server_health to verify the Hexstrike MCP server is connected and responsive.
Step 3: Active Processes
Run list_active_processes to show all currently running scans and tools. Display their status, progress, and target.
Step 4: System Metrics
Run display_system_metrics for CPU, memory, disk, and network usage. Flag any resource constraints that could affect scan performance.
Step 5: Engagement Files
Use Glob to find all report files in the project directory (*.md, *-report.*, *-scan.*). List them with modification dates to show engagement progress.
Step 6: Dashboard Output
Present a unified dashboard view:
=== Hexstrike Server: [status] ===
--- Active Scans ---
[list of running processes with targets and progress]
--- System Resources ---
CPU: [usage] | RAM: [usage] | Disk: [usage]
--- Engagement Files ---
[list of recon/scan output files with dates]
--- Cache ---
[hit rate and size]
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 · 49 lines · 10 tokens per session scan A 3c1e42a11ab7
dashboard 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 349 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.