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 trentonWrote 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/op-status)<a href="https://agentmods.dev/commands/ogrodev/fsociety/op-status"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/op-status/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/op-status"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/op-status.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.00018 | $0.00158 |
| Opus 5.5 | $0.00007 | $0.00063 |
| Sonnet 5.5 | $0.00004 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
op-status 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
Op Status
- Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/session-state.js" showfor full session state - Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/ops-tracker.js" summaryfor operations summary - Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/opsec-profile.js" getfor current opsec profile - Output condensed single-line status:
<operation-name> | Phase <n>/<total> | <N> ops (<N> FAIL) | <proxy-chain> | <profile> - If active blockers, show on second line
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 · 13 lines · 18 tokens per session scan A 0fe0d4b516b0
op-status is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 158 once invoked, about $0.0001 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
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
scout-meta-review
Run an interactive Scout meta-review — a system-level audit that sits above the individual session types. Checks whether sessions are running, mistake audit is trending well, proposals are flowing, KB files are healthy, and data-source coverage is consistent across session types. Runs in the current conversation.
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.
brief
Cold-start session orientation — use when starting fresh or returning after a long absence (days or weeks). Scales depth to how long you've been away. Not for quick mid-session checks (use /tools:status) or planning (use /tools:overview).
agent-triage
Find and triage Quickchat conversations that need a human.