Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Liberty91LTD/cti-skillsnpx agentmods add skills/liberty91ltd/cti-skills/lookup-greynoiseWrote 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/skills/liberty91ltd/cti-skills/lookup-greynoise)<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/lookup-greynoise"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/lookup-greynoise/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.
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/lookup-greynoise"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/lookup-greynoise.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00066 | $0.01424 |
| Opus 5.5 | $0.00026 | $0.00570 |
| Sonnet 5.5 | $0.00013 | $0.00285 |
| Haiku 4.5 | $0.00007 | $0.00142 |
Grade A, and why
lookup-greynoise 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lookup-greynoise
Queries GreyNoise to classify whether an IP is internet background noise (opportunistic scanners, search engines, etc.) or targeted. IP-only. Retrieval only.
When to invoke
- User asks if an IP is scanner noise or targeted
- Investigation skill wants to filter out mass-scanning IPs from indicator lists
- Deciding if an IP hitting your perimeter is worth investigating
How to invoke
Two CLIs are provided. Pick by capability needed:
Basic noise check — Node CLI (zero deps)
node tools/clis/greynoise.js ip <ip>
Hits the /v3/community/{ip} endpoint (free, 50/day). Best for fast retrieval inside an investigation chain.
Full surface — Python CLI (uses official pygreynoise SDK)
python3 tools/clis/greynoise.py community <ip> # FREE (50/day)
python3 tools/clis/greynoise.py context <ip> # Enterprise
python3 tools/clis/greynoise.py riot <ip> # Enterprise
python3 tools/clis/greynoise.py quick <ip,ip,...> # Enterprise (bulk)
python3 tools/clis/greynoise.py similarity <ip> # Enterprise
python3 tools/clis/greynoise.py timeline <ip> [--days N] # Enterprise
python3 tools/clis/greynoise.py query "<gnql>" # Enterprise
python3 tools/clis/greynoise.py stats "<gnql>" # Enterprise
python3 tools/clis/greynoise.py metadata
Self-bootstraps a private venv at tools/clis/.venv-greynoise/ on first run.
Capabilities the Node CLI doesn't have (Enterprise tier required for most):
- Context — full per-IP telemetry: every port/protocol/payload combination GreyNoise has observed, broken down by date.
- GNQL search (
query) — find every IP matching a query:classification:malicious tags:Mirai metadata.country:RU. The killer pivot — discover scanner clusters by characteristic. - GNQL stats — bucket counts (countries, ASNs, tags, categories) for a query without pulling individual results.
- Similarity — given an IP, find behaviorally similar scanners (often used to expand a single observation into a cluster).
- Timeline — daily activity history for an IP — useful for distinguishing a brief campaign from persistent scanning.
- Quick (bulk) — classify many IPs in one call (cheaper than N individual lookups).
- RIOT — explicit known-benign check (CDNs, search engines, ISPs) without the noise classification.
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.
- 2mo ago First seen · 122 lines · 66 tokens per session scan A 1c36a85aad48
lookup-greynoise is a skill published in the GitHub repository Liberty91LTD/cti-skills (36 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 1,424 once invoked, about $0.0003 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-30.
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…
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.
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…
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.
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…
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.