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/findings)<a href="https://agentmods.dev/commands/ogrodev/fsociety/findings"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/findings/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/findings"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/findings.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.00000 | $0.00459 |
| Opus 5.5 | $0.00000 | $0.00184 |
| Sonnet 5.5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
findings 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
You are querying the Elliot findings database (findings-db.jsonl). Use the findings-tracker.js script to retrieve and display results.
The tracker script is located at: ${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js
Argument Handling
Parse the user's arguments from $ARGUMENTS:
-
No arguments: Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" listfirst to show the table, thennode "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" summaryfor the stats. -
--severity <level>: Runnode "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list --severity <level> -
--type <vuln_type>: Runnode "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list --type <vuln_type> -
Any other text (search term): Run
node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" search <term> -
summary: Runnode "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" summary -
--html(anywhere in arguments): Runnode "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" htmlwith any additional filters (--severity,--type,--status) passed through. The script writes an HTML file and prints the path. Show the path to the user.
Output Format
Present the results in a clean, readable format. If the tracker outputs a table, pass it through directly. For summary output, present the counts prominently.
If no findings exist yet, mention that findings are auto-recorded when Hexstrike scans detect vulnerabilities, and suggest running a scan command like /webscan or /apiscan.
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 · 32 lines · 0 tokens per session scan A ffaefbc2264d
findings is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 459 tokens. 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
review-data-model
Evaluate a data model or schema design for normalization, naming, relationships, and extensibility.
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.
archetype-impact
Scan the current workspace for all references to a given archetype across templates (.oet / .t.json source, .opt compiled) and AQL files, producing an impact table useful before editing a widely-reused archetype.
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.
sparc-supabase-admin
🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...
generate-data-model
Generate ORM schemas (Prisma, SQLAlchemy, Mongoose, Drizzle) from blueprint shared types and database definitions.