agentleFS
Sign inStart free
Liberty91LTDLiberty91LTD/cti-skills/skills/greynoise-api/SKILL.md

greynoise-api

Skill35 starsChanged 44 days agoMITView on GitHub

GreyNoise API reference. Internet scanner/noise classification for IPs.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If noise:true → opportunistic, not targeted

    line 56
  2. Very specific:

    If noise:false → potentially targeted, higher priority

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

ClassificationMeaningAction
benign + noise:trueKnown benign scanner (Shodan, Censys, etc.)Likely false positive — deprioritise
malicious + noise:trueKnown malicious scannerReal threat, but opportunistic, not targeted
unknown + noise:trueUnclassified scannerInvestigate further
noise:false + riot:falseNot a known scannerMay be targeted — investigate
riot:trueKnown benign serviceDefinitely 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free