agentmods.dev

techniques

A command for viewing and searching a database of security techniques and reports. It can filter entries by result or tool and show coverage and report information.

In plain words
What is it for?
Use it to list techniques, search by a term, filter by tool or result, inspect coverage, or view HTML output.
Why use it?
It makes recorded techniques and past results easier to find than searching the database manually.

Command

20 5mo ago A scan 8 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/techniques
Clone the repo
git clone --depth 1 https://github.com/ogrodev/fsociety
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 462 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.00008 $0.00462
Opus 5 $0.00004 $0.00231
Sonnet 5 $0.00002 $0.00092
Haiku 4.5 $0.00001 $0.00046

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

Security

Grade A, and why

techniques 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/techniques.md · 34 lines

What it actually says

You are querying the Elliot techniques database (techniques-db.jsonl). Use the techniques-tracker.js script to retrieve and display results.

The tracker script is located at: ${CLAUDE_PLUGIN_ROOT}/scripts/techniques-tracker.js

Argument Handling

Parse the user's arguments from $ARGUMENTS:

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

  2. --result <type>: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/techniques-tracker.js" list --result <type>

  3. --tool <name>: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/techniques-tracker.js" list --tool <name>

  4. coverage: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/techniques-tracker.js" coverage

  5. reports: Run node "${CLAUDE_PLUGIN_ROOT}/scripts/techniques-tracker.js" reports

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

  7. --html (anywhere in arguments): Run node "${CLAUDE_PLUGIN_ROOT}/scripts/techniques-tracker.js" html with any additional filters (--result, --tool) passed through. The script writes an HTML file and prints the path. Show the path to the user.

Output Format

Present the results clearly. For coverage output, highlight gaps prominently. For reports, list file paths so the user can quickly access them.

If no techniques are logged yet, explain that techniques are auto-recorded after Hexstrike scans and can also be manually added.

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 · 34 lines · 0 tokens per session scan A 392d57e3b7ee

Subscribe to this mod's changes

techniques is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 462 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.

DatabasesSecurityTestingclaude-codeclaude-code-pluginoffensive-securitypentesting
Related

Other commands, from other repositories

pr

Create a PR to main branch using conventional commit style for the title.

KeygraphHQ/shannon · 13 tokens

engage.scope

Execute Phase 0 - Scope Definition and Rules of Engagement.

hypnguyen1209/offensive-claude · 11 tokens

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.

Stickman230/claude-pentest · 58 tokens

pentest-exit

Close pentest session — summarizes findings, ensures outputs are saved, lifts isolation, and prompts for /clear.

Stickman230/claude-pentest · 26 tokens

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.

allsmog/blackbox-claude-plugin · 44 tokens

bb-spray

Credential spraying across discovered services.

allsmog/blackbox-claude-plugin · 9 tokens