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.
npx agentmods add commands/ogrodev/fsociety/intelgit clone --depth 1 https://github.com/ogrodev/fsocietyWhat 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 | $0.00006 | $0.00291 |
| Opus 5 | $0.00003 | $0.00146 |
| Sonnet 5 | $0.00001 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
intel 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.
What it actually says
Target Intel Manager
Manage the engagement's persistent target intelligence database. Intel accumulates across sessions and scans.
The user's argument: $ARGUMENTS
Dispatch
If no arguments or summary:
node "${CLAUDE_PLUGIN_ROOT}/scripts/target-intel.js" summary
If show <target>:
node "${CLAUDE_PLUGIN_ROOT}/scripts/target-intel.js" show <target>
If search <keyword>:
node "${CLAUDE_PLUGIN_ROOT}/scripts/target-intel.js" search <keyword>
If list (with optional filters):
node "${CLAUDE_PLUGIN_ROOT}/scripts/target-intel.js" list $ARGUMENTS
If add <target> <category> <key> <value>:
node "${CLAUDE_PLUGIN_ROOT}/scripts/target-intel.js" add $ARGUMENTS
If forget <target>:
node "${CLAUDE_PLUGIN_ROOT}/scripts/target-intel.js" forget <target>
Present the output directly. No additional commentary needed.
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.
- 2d ago First seen · 46 lines · 6 tokens per session scan A 3ee4392e661d
intel 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 291 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.
Other commands, from other repositories
pr
Create a PR to main branch using conventional commit style for the title.
engage.scope
Execute Phase 0 - Scope Definition and Rules of Engagement.
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-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.
bb-spray
Credential spraying across discovered services.