greynoise-api

greynoise-api is a skill for Claude Code from Liberty91LTD/cti-skills. It costs 19 tokens per session (578 once invoked), scanned A, original, MIT.

An API reference for GreyNoise, a service that checks whether an IP address is known internet scanning activity and classifies it as benign, malicious, or unknown.

In plain words
What is it for?
It supports looking up IP addresses, reading scanner classifications and details, and using the results to prioritize security investigations.
Why use it?
It helps distinguish harmless automated scanners from potentially hostile scanning instead of treating every scan as the same threat.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

Good fit It supports looking up IP addresses, reading scanner classifications and details, and using the results to prioritize security investigations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/liberty91ltd/cti-skills/greynoise-api
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.

Any agent
npx skills add Liberty91LTD/cti-skills --skill greynoise-api
Clone the repo
git clone --depth 1 https://github.com/Liberty91LTD/cti-skills

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 greynoise-api

README.md
[![agentmods](https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/greynoise-api/github.svg)](https://agentmods.dev/skills/liberty91ltd/cti-skills/greynoise-api)
Your own site
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/greynoise-api"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/greynoise-api/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 greynoise-api

Your own site · 80×15
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/greynoise-api"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/greynoise-api.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 578 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00019 $0.00578
Opus 5.5 $0.00008 $0.00231
Sonnet 5.5 $0.00004 $0.00116
Haiku 4.5 $0.00002 $0.00058

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

Security

Grade A, and why

greynoise-api 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 2mo 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.

Makes network callslowCapability

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

curl -s "https://api.greynoise.io/v3/community/{ip}" \
skills/greynoise-api/SKILL.md · 70 lines

What it actually says

GreyNoise API

Base URL

  • Community: https://api.greynoise.io/v3/community
  • Enterprise: https://api.greynoise.io/v3

Authentication

Header: key: $GREYNOISE_API_KEY

Rate Limits

  • Community (free): 50 requests/day
  • Enterprise: Based on plan

Key Endpoints

Community IP Lookup (Free)

curl -s "https://api.greynoise.io/v3/community/{ip}" \
  -H "key: $GREYNOISE_API_KEY"

Response fields:

  • noise — true if IP is a known internet scanner
  • riot — true if IP belongs to a known benign service (CDN, DNS, etc.)
  • classification — benign|malicious|unknown
  • name — actor name if identified
  • last_seen — last observation date
  • message — human-readable summary

Enterprise Context (Paid)

curl -s "https://api.greynoise.io/v3/noise/context/{ip}" \
  -H "key: $GREYNOISE_API_KEY"

Additional fields: tags, cve, os, ports, raw_data

Classification Meaning

Classification Meaning Action
benign + noise:true Known benign scanner (Shodan, Censys, etc.) Likely false positive — deprioritise
malicious + noise:true Known malicious scanner Real threat, but opportunistic, not targeted
unknown + noise:true Unclassified scanner Investigate further
noise:false + riot:false Not a known scanner May be targeted — investigate
riot:true Known benign service Definitely deprioritise

CTI Value

GreyNoise answers: "Is this IP scanning the whole internet, or is it specifically targeting us?"

  • If noise:true → opportunistic, not targeted
  • If noise:false → potentially targeted, higher priority

Response Summary Format

ip: <IP>
noise: <true/false>
riot: <true/false>
classification: benign|malicious|unknown
name: <actor name or "unknown">
last_seen: <date>
message: <summary>
verdict: benign-scanner|malicious-scanner|not-scanner|benign-service
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. 2mo ago First seen · 70 lines · 19 tokens per session scan A 5cc188adb0d0

Subscribe to this mod's changes

greynoise-api is a skill published in the GitHub repository Liberty91LTD/cti-skills (36 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 578 once invoked, about $0.0001 per session on Opus 5.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-08-30.

Related

Other skills, from other repositories

analyzing-campaign-attribution-evidence

Systematically evaluate cyber-campaign evidence to attribute an operation to a threat actor, using the Diamond Model and Analysis of Competing Hypotheses (ACH) to weigh infrastructure overlaps, TTP consistency, malware code similarity, and timing/language artifacts into confidence-weighted attribution assessments. Use…

mukul975/Anthropic-Cybersecurity-Skills · 79 tokens

analyzing-threat-actor-ttps-with-mitre-attack

MITRE ATT&CK is a globally-accessible knowledge base of adversary tactics, techniques, and procedures (TTPs) based on real-world observations. This skill covers systematically mapping threat actor beh.

26zl/cybersec-toolkit · 54 tokens

analyzing-threat-landscape-with-misp

Analyze the threat landscape using MISP (Malware Information Sharing Platform) by querying event statistics, attribute distributions, threat actor galaxy clusters, and tag trends over time. Uses PyMISP to pull event data, compute IOC type breakdowns, identify top threat actors and malware families, and generate threat…

26zl/cybersec-toolkit · 75 tokens

analyzing-campaign-attribution-evidence

Use when campaign attribution analysis involves systematically evaluating evidence to determine which threat actor or group is responsible for a cyber operation. This skill covers collecting and weighting attr.

oyi77/1ai-skills · 40 tokens

prompt-injection-auditor

Security audit of LLM system prompts, agent instruction files (SKILL.md, AGENTS.md, CLAUDE.md), and agent configurations against prompt injection attacks. Use when the user wants to (1) audit or harden a system prompt or agent instructions against prompt injection, (2) review an agent skill or system prompt for…

screem500/prompt-injection-auditor · 159 tokens

analyzing-campaign-attribution-evidence

Campaign attribution analysis involves systematically evaluating evidence to determine which threat actor or group is responsible for a cyber operation. This skill covers collecting and weighting attr.

26zl/cybersec-toolkit · 38 tokens