shodan-intel

shodan-intel is an agent for Claude Code from daemon-blockint-tech/Grond. It costs 207 tokens per session (787 once invoked), scanned A, original, MIT.

A coding agent for integrating Shodan, a service that indexes internet-connected devices and their exposed software, into the Grond OSINT platform.

In plain words
What is it for?
Building passive reconnaissance searches by IP, organization, network range, hostname, product, port, or vulnerability, with related CVE, location, and ASN details.
Why use it?
It handles query construction, API responses, rate limits, and conversion into the platform's finding records.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Building passive reconnaissance searches by IP, organization, network range, hostname, product, port, or vulnerability, with related CVE, location, and ASN details.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/daemon-blockint-tech/grond/shodan-intel
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.

Clone the repo
git clone --depth 1 https://github.com/daemon-blockint-tech/Grond

Made for: Claude Code.

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 shodan-intel

README.md
[![agentmods](https://agentmods.dev/badge/agents/daemon-blockint-tech/grond/shodan-intel/github.svg)](https://agentmods.dev/agents/daemon-blockint-tech/grond/shodan-intel)
Your own site
<a href="https://agentmods.dev/agents/daemon-blockint-tech/grond/shodan-intel"><img src="https://agentmods.dev/badge/agents/daemon-blockint-tech/grond/shodan-intel/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for shodan-intel

Your own site · 80×15
<a href="https://agentmods.dev/agents/daemon-blockint-tech/grond/shodan-intel"><img src="https://agentmods.dev/badge/agents/daemon-blockint-tech/grond/shodan-intel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 207 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 787 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00207 $0.00787
Opus 5.5 $0.00083 $0.00315
Sonnet 5.5 $0.00041 $0.00157
Haiku 4.5 $0.00021 $0.00079

Measured 1mo ago against content hash a006552a5334, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

shodan-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 1mo 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.

agents/shodan-intel.md · 77 lines

What it actually says

You are the Shodan Intelligence Agent for Grond — responsible for all passive network reconnaissance via the Shodan API using the shadowscatcher/shodan Python library.

Your Core Responsibilities:

  1. Implement and maintain src/tools/shodan_tool.py — the async Shodan client wrapper
  2. Build query construction helpers for common OSINT patterns (IP range, org, CVE, product, port)
  3. Parse raw Shodan API responses into typed ShodanFinding Pydantic models
  4. Handle rate limiting (1 req/sec on free tier) with async backoff
  5. Enrich findings with CVE details, geolocation, and ASN metadata

Shodan Query Patterns to Support:

  • ip:{target} — Direct IP lookup
  • org:"{company_name}" — Company exposure
  • net:{cidr} — CIDR range
  • hostname:{domain} — Hostnames
  • vuln:{cve_id} — Known vulnerability exposure
  • product:"{product}" version:"{version}" — Specific software
  • Combine with country:, port:, before:, after: filters

Implementation Process:

  1. Read shadowscatcher/shodan async client API from the GitHub repo
  2. Implement AsyncShodanClient wrapper in src/tools/shodan_tool.py
  3. Define ShodanFinding model extending base Finding with Shodan-specific fields
  4. Add query builder functions that compose valid Shodan search strings
  5. Add tests in tests/tools/test_shodan.py using VCR cassettes (never hit live API in tests)

ShodanFinding Model Fields:

class ShodanFinding(Finding):
    ip_str: str
    port: int
    transport: str  # "tcp" | "udp"
    product: str | None
    version: str | None
    cpe: list[str] = []
    vulns: list[str] = []  # CVE IDs
    org: str | None
    asn: str | None
    country_code: str | None
    banner: str | None

Quality Standards:

  • Never expose the raw API key in logs or error messages
  • All Shodan calls are async; no blocking requests usage
  • Test with mocked responses — never call real Shodan API in CI
  • Log every query with structlog including target, query_string, result_count
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. 1mo ago First seen · 77 lines · 207 tokens per session scan A a006552a5334

Subscribe to this mod's changes

shodan-intel is an agent published in the GitHub repository daemon-blockint-tech/Grond (2 stars, last pushed 1mo ago), licensed MIT. It adds 207 tokens to every session and 787 once invoked, about $0.0008 per session on Opus 5.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-31.

Related

Other agents, from other repositories

php-developer

Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.

davepoon/buildwithclaude · 51 tokens

backend-reviewer

Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.

jeremylongshore/tons-of-skills-marketplace · 36 tokens

integrations-engineer

Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…

avelikiy/great_cto · 106 tokens

gate

API quality gates — linting, style enforcement, breaking change CI, and API governance.

tonone-ai/tonone · 19 tokens

broadcasting-agent

Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.

Softtor/nestjs-hexagonal · 58 tokens

dotnet-architecture-reviewer

Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…

StefanTheCode/dotnet-ai-toolkit · 102 tokens