agentmods.dev

findings

A command-line viewer for the Elliot findings database, a file that records reported issues. It can list, search, filter, summarize, and export findings as HTML.

In plain words
What is it for?
Use it to review security findings, find a particular issue, inspect summary statistics, or create an HTML view of selected results.
Why use it?
It avoids opening and searching the database file by hand. Filters help narrow results by severity, issue type, or status.

Command

20 5mo ago A scan 6 tokens original MIT
View the source file ogrodev/fsociety
Install

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.

agentmods
npx agentmods add commands/ogrodev/fsociety/findings
Clone the repo
git clone --depth 1 https://github.com/ogrodev/fsociety
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 459 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.00459
Opus 5 $0.00003 $0.00230
Sonnet 5 $0.00001 $0.00092
Haiku 4.5 $0.00001 $0.00046

Measured 2d ago against content hash ffaefbc2264d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

elliot/commands/findings.md · 32 lines

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:

  1. No arguments: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list first to show the table, then node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" summary for the stats.

  2. --severity <level>: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list --severity <level>

  3. --type <vuln_type>: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" list --type <vuln_type>

  4. Any other text (search term): Run node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" search <term>

  5. summary: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" summary

  6. --html (anywhere in arguments): Run node "${CLAUDE_PLUGIN_ROOT}/scripts/findings-tracker.js" html with 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.

Changes

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.

  1. 2d ago First seen · 32 lines · 0 tokens per session scan A ffaefbc2264d

Subscribe to this mod's changes

findings is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 6 tokens to every session and 459 once invoked, about $0.0000 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-08-30.

Debuggingclaude-codeclaude-code-pluginoffensive-securitypentesting
Related

Other commands, from other repositories

review

Review code changes for Shannon-specific patterns, security, and common mistakes.

KeygraphHQ/shannon · 13 tokens

debug

Systematically debug errors using context analysis and structured recovery.

KeygraphHQ/shannon · 10 tokens

engage.c2

Execute Phase 6 - Command and Control Infrastructure Setup.

hypnguyen1209/offensive-claude · 10 tokens

engage.install

Execute Phase 5 - Installation and Persistence Establishment.

hypnguyen1209/offensive-claude · 10 tokens

engage.weaponize

Execute Phase 2 - Weaponization and Payload Development.

hypnguyen1209/offensive-claude · 10 tokens

engage.deliver

Execute Phase 3 - Delivery and Payload Deployment.

hypnguyen1209/offensive-claude · 9 tokens