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-urlscanWrote 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-urlscan)<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/lookup-urlscan"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/lookup-urlscan/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-urlscan"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/lookup-urlscan.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.00065 | $0.01234 |
| Opus 5.5 | $0.00026 | $0.00494 |
| Sonnet 5.5 | $0.00013 | $0.00247 |
| Haiku 4.5 | $0.00006 | $0.00123 |
Grade A, and why
lookup-urlscan 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
lookup-urlscan
Submits URLs to URLScan.io for live scanning and retrieves results. For domains, searches existing scans first (uses cached scan if <24h old, else submits new one). Retrieval only — do not interpret.
When to invoke
- User asks to scan a URL or check what a domain renders as
- Investigation skill needs redirect chain, contacted infra, or a visual snapshot
- Triaging a potentially malicious URL before clicking
How to invoke
Two CLIs are provided. Pick by capability needed:
Basic submit + cached domain search — Node CLI (zero deps)
node tools/clis/urlscan.js url "<url>"
node tools/clis/urlscan.js domain <domain>
Single-shot URL submit (with built-in 30s wait + 5x10s polling) or domain search. Best for fast retrieval inside an investigation chain.
Full API surface — Python CLI (stdlib only)
python3 tools/clis/urlscan.py submit <url> [--visibility V] [--country CC]
[--tags t1,t2] [--user-agent UA]
[--referer R] [--wait]
python3 tools/clis/urlscan.py result <uuid>
python3 tools/clis/urlscan.py search "<lucene-query>" [--size N]
python3 tools/clis/urlscan.py quota
python3 tools/clis/urlscan.py screenshot <uuid> [--out FILE]
python3 tools/clis/urlscan.py dom <uuid> [--out FILE]
Stdlib only — no install, no venv.
Capabilities the Node CLI doesn't have:
- Lucene-style search — the killer pivot. Query against URLScan's full database:
page.domain,page.url,asn,hash,filename,verdicts.overall.malicious,task.tags,page.country, etc. Combine with AND/OR/NOT. - Result by UUID — fetch a known scan without re-submitting.
- Quota check — see remaining scan/search/retrieve quota before committing to a batch.
- Screenshot download (
screenshot --out img.png) — pull the rendered page screenshot. - DOM download (
dom --out page.html) — pull captured HTML for offline analysis. - Submission options — country, custom user-agent, custom referer, tags.
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 · 123 lines · 65 tokens per session scan A 5ea25109cef4
lookup-urlscan is a skill published in the GitHub repository Liberty91LTD/cti-skills (36 stars, last pushed 4d ago), licensed MIT. It adds 65 tokens to every session and 1,234 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.