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/bruteforcegit 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.00009 | $0.00483 |
| Opus 5 | $0.00005 | $0.00242 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
bruteforce 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
Brute Force Attack
Service: $1
Target: $2
Execute password attacks using Hexstrike MCP tools.
Step 1: Load Tools
Use ToolSearch to load:
hydra_attack— online password brute forcingjohn_crack— offline password/hash crackinghashcat_crack— GPU-accelerated hash crackingnetexec_scan— network credential testing (SMB/SSH/WinRM)
Step 2: Identify Attack Type
Map the service to the appropriate approach:
Online brute force (live service login):
- ssh, ftp, http-post-form, http-get, rdp, smb, telnet, vnc, mysql, mssql, postgres
- Tool:
hydra_attack
Offline hash cracking (captured hashes):
- md5, sha1, sha256, sha512, bcrypt, ntlm, kerberos, wordpress
- Tool:
john_crackorhashcat_crack
Network credential testing:
- smb, ssh, winrm, ldap, mssql, rdp
- Tool:
netexec_scan
Step 3: Online Brute Force (if applicable)
Run hydra_attack with:
- Target service and port
- Username list or single username
- Password list (check for existing wordlists in
attack/directory) - Appropriate thread count (lower for rate-limited services)
- Service-specific options (e.g., http-post-form with login path and failure string)
Step 4: Hash Cracking (if applicable)
For captured hashes, choose the right tool:
- john_crack — good for many hash types, rule-based attacks
- hashcat_crack — faster for GPU-friendly hashes, more attack modes
Run with:
- Hash file or hash value
- Wordlist + rules for dictionary attack
- Or mask for brute force pattern
Step 5: Results
Report found credentials clearly:
| Username | Password | Service | Status |
|---|
IMPORTANT: Handle credentials responsibly. Only test credentials within authorized scope.
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 · 60 lines · 9 tokens per session scan A 169e21655b86
bruteforce is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 9 tokens to every session and 483 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
review
Review code changes for Shannon-specific patterns, security, and common mistakes.
debug
Systematically debug errors using context analysis and structured recovery.
engage.c2
Execute Phase 6 - Command and Control Infrastructure Setup.
engage.install
Execute Phase 5 - Installation and Persistence Establishment.
engage.weaponize
Execute Phase 2 - Weaponization and Payload Development.
engage.deliver
Execute Phase 3 - Delivery and Payload Deployment.