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/ty-darkwebgit clone --depth 1 https://github.com/ogrodev/fsocietyWrote 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/ty-darkweb)<a href="https://agentmods.dev/commands/ogrodev/fsociety/ty-darkweb"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-darkweb.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00895 |
| Opus 5 | $0.00009 | $0.00447 |
| Sonnet 5 | $0.00003 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade B, and why
ty-darkweb scanned grade B with 2 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo service tor start Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --socks5 127.0.0.1:9050 --socks5-hostname 127.0.0.1:9050 \ How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are executing a dark web leak search for the tyrell data exfiltration plugin.
Step 1 — Profile Gate Check
The dark web hunting module requires a dark or ghost operational profile. Verify before proceeding:
node "${CLAUDE_PLUGIN_ROOT}/scripts/hunt-engine.js" darkweb --check-profile $ARGUMENTS
If the active profile is anything other than dark or ghost, stop immediately:
Dark web access requires a dark or ghost operational profile. This protects operator identity. Switch profiles and ensure Tor routing is active before continuing.
Step 2 — Verify Tor Routing
Confirm that traffic will be routed through Tor before making any .onion requests:
# Verify Tor is running and accessible
curl --socks5 127.0.0.1:9050 --socks5-hostname 127.0.0.1:9050 \
-s https://check.torproject.org/api/ip | jq '.IsTor'
If this returns false, start the Tor service:
sudo service tor start
# Wait for circuit establishment
sleep 10
Alternatively, verify proxychains configuration is pointing to Tor's SOCKS5 proxy at 127.0.0.1:9050.
Step 3 — Generate Dark Web Search Queries
Run the hunt engine for .onion-specific search targets:
node "${CLAUDE_PLUGIN_ROOT}/scripts/hunt-engine.js" darkweb $ARGUMENTS
The script returns: onion_urls (known leak index sites), search_queries, and keywords tailored for dark web leak markets.
Step 4 — Execute Searches via Tor
For each dark web search engine or index in the returned list, execute via torsocks or proxychains:
# Via torsocks
torsocks curl -s "http://<onion-search-engine>.onion/search?q=<query>" \
-H "User-Agent: Mozilla/5.0" | grep -oP 'http://[a-z2-7]{16,56}\.onion[^\s"<>]*'
# Via proxychains
proxychains curl -s "http://<onion-url>.onion/search?q=<query>"
Common dark web leak indexes to query (use addresses from hunt-engine output):
- Ahmia (clearnet-accessible Tor search)
- Torch, Haystak (Tor-native search engines)
- Known leak market .onion addresses from the hunt engine
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.
- today First seen · 105 lines · 17 tokens per session scan B 22ea4fce8b51
ty-darkweb is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 17 tokens to every session and 895 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
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-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.
pentest-kali
Connect to a Metasploit-Kali Server (MKS) REST API — verifies connectivity, discovers available Kali tools, and configures agents to prefer MKS endpoints over local Bash equivalents.
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.
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.