ty-shodan

ty-shodan is a command for coding agents from ogrodev/fsociety. It costs 12 tokens per session (620 once invoked), scanned A, original, MIT.

Search Shodan/Censys for exposed databases matching a query.

Command

Installs and runs on its own, but its text points at files inside the plugin that ships it — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed.

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/ty-shodan
Clone the repo
git clone --depth 1 https://github.com/ogrodev/fsociety

Wrote 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.

agentmods badge for ty-shodan

README.md
[![agentmods](https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-shodan.svg)](https://agentmods.dev/commands/ogrodev/fsociety/ty-shodan)
Your own site
<a href="https://agentmods.dev/commands/ogrodev/fsociety/ty-shodan"><img src="https://agentmods.dev/badge/commands/ogrodev/fsociety/ty-shodan.svg" alt="Measured on agentmods" height="20"></a>
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 620 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin unknown 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.00012 $0.00620
Opus 5 $0.00006 $0.00310
Sonnet 5 $0.00002 $0.00124
Haiku 4.5 $0.00001 $0.00062

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

Security

Grade A, and why

ty-shodan scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

If the Shodan CLI is unavailable, fall back to the Shodan REST API via curl:
tyrell/commands/ty-shodan.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are executing a Shodan/Censys exposed database hunt for the tyrell data exfiltration plugin.

Step 1 — Generate Queries

Run the hunt engine to produce optimized Shodan/Censys search queries for the given target:

node "${CLAUDE_PLUGIN_ROOT}/scripts/hunt-engine.js" shodan $ARGUMENTS

Parse the output carefully. The script will return one or more structured query objects with fields: platform (shodan|censys), query, service, and rationale.

Step 2 — Execute Queries

For each query returned:

  • If platform is shodan, execute using the Shodan CLI:

    shodan search --fields ip_str,port,org,hostnames,data "<query>"
    

    If the Shodan CLI is unavailable, fall back to the Shodan REST API via curl:

    curl -s "https://api.shodan.io/shodan/host/search?key=${SHODAN_API_KEY}&query=<query>" | jq '.matches[] | {ip: .ip_str, port: .port, org: .org, banner: .data}'
    
  • If platform is censys, use the Censys CLI or REST API:

    censys search "<query>" --index-type hosts
    

    Or via curl:

    curl -s -u "${CENSYS_API_ID}:${CENSYS_API_SECRET}" "https://search.censys.io/api/v2/hosts/search?q=<query>" | jq '.result.hits[] | {ip: .ip, services: .services}'
    

Step 3 — Log Discovered Sources

For each host that appears to expose a database service without authentication or with weak credentials, log it using source-tracker:

node "${CLAUDE_PLUGIN_ROOT}/scripts/source-tracker.js" add \
  --type shodan \
  --host "<ip>:<port>" \
  --service "<service-type>" \
  --query "<original-query>" \
  --notes "<any relevant banner or metadata>"

Step 4 — Present Results

Display a structured summary table of all discovered sources:

Source ID Host Port Service Org Status
... ... ... ... ... ...

Highlight any hosts that show authentication bypass indicators (e.g., open MongoDB without auth, Elasticsearch with no X-Pack security, Redis with no requirepass).

Read the full file on GitHub · 65 lines

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. today First seen · 65 lines · 12 tokens per session scan A c0af2c884551

Subscribe to this mod's changes

ty-shodan is a command published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 620 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

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.

Stickman230/claude-pentest · 58 tokens

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.

Stickman230/claude-pentest · 60 tokens

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.

Stickman230/claude-pentest · 43 tokens

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.

Stickman230/claude-pentest · 51 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