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.
npx skills add Liberty91LTD/cti-skills --skill urlscan-apigit clone --depth 1 https://github.com/Liberty91LTD/cti-skillsWrote 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/urlscan-api)<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/urlscan-api"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/urlscan-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.
<a href="https://agentmods.dev/skills/liberty91ltd/cti-skills/urlscan-api"><img src="https://agentmods.dev/badge/skills/liberty91ltd/cti-skills/urlscan-api.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.00019 | $0.00601 |
| Opus 5 | $0.00010 | $0.00300 |
| Sonnet 5 | $0.00004 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
urlscan-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 7d 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 -X POST "https://urlscan.io/api/v1/scan/" \ What it actually says
URLScan.io API
Base URL
https://urlscan.io/api/v1
Authentication
Header: API-Key: $URLSCAN_API_KEY
Rate Limits
- Free: 100 scans/day, 100 searches/day
- Paid: Higher limits based on plan
Key Endpoints
Submit URL for scanning
curl -s -X POST "https://urlscan.io/api/v1/scan/" \
-H "API-Key: $URLSCAN_API_KEY" \
-H "Content-Type: application/json" \
-d '{"url": "https://example.com", "visibility": "unlisted"}'
Response: {"uuid": "...", "api": "https://urlscan.io/api/v1/result/UUID/"}
Important: Scan is async. Wait ~30 seconds before retrieving results. Poll the result URL until status is not 404.
Retrieve scan results
curl -s "https://urlscan.io/api/v1/result/{uuid}/" \
-H "API-Key: $URLSCAN_API_KEY"
Useful response fields:
verdicts.overall— malicious/benign scorepage.url— final URL after redirectspage.ip— IP address resolvedpage.country— hosting countrypage.server— web serverlists.ips— all IPs contactedlists.domains— all domains contactedlists.urls— all URLs loadedstats.tlsPercentage— TLS usagetask.screenshotURL— screenshot of page
Search existing scans
curl -s "https://urlscan.io/api/v1/search/?q=domain:example.com" \
-H "API-Key: $URLSCAN_API_KEY"
Search operators: domain:, ip:, server:, filename:, hash:, page.url:
Scan Flow
- Submit URL → get UUID
- Wait 30 seconds
- Poll result endpoint (retry on 404, max 5 attempts with 10s delay)
- Extract and return key findings
Response Summary Format
url: <scanned URL>
final_url: <after redirects>
verdict: malicious|suspicious|benign|unknown
ip: <resolved IP>
country: <hosting country>
technologies: [<detected technologies>]
domains_contacted: [<list>]
ips_contacted: [<list>]
screenshot: <URL>
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.
- 7d ago First seen · 76 lines · 19 tokens per session scan A 7d35dae7ca1d
urlscan-api is a skill published in the GitHub repository Liberty91LTD/cti-skills (17 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 601 once invoked, about $0.0001 per session on Opus 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-09-03.
Other skills, from other repositories
ai-browser-use
A business-diagnosis assistant for marketing, operations, product, and sales questions about how to approach a task.
test-engineer
Automated E2E testing with Playwright including the auto-fix loop — generate test cases from the UI, run them, fix failures and re-run until passing, then produce a human-readable report. Test until it passes, not just test and report. Drives /toh-test; use whenever tests must be written, run, or made green.
hatch3r-browser-verify
Opt-in browser verification skill — spec-run-first Playwright verification (assertions execute in the runner, agent reads only failures), axe-core a11y audits, toHaveScreenshot() regression diffs, E2E test scaffolds, and snapshot-mode exploratory driving. Default ON for UI-affecting agent invocations; disable globally…
browser-qa
Validate web applications through the embedded browser with responsive, interaction, console, and screenshot checks.
browser
Drive the user's REAL authenticated browser (their logins/cookies) via the local-browser chain — guilde → tunnel → daemon → chrome-devtools-mcp → cloned Chrome. The foundation skill for any "do X in a browser as me" task: navigate, capture (element screenshots + selective content/ld+json/readability), inspect network…
Drive the user's real authenticated LinkedIn — via camofox stealth (preferred, distinct session + WhatsApp re-auth alert) or the chrome-devtools chain (fallback). API-first: read feed/profiles/activity, who-reacted/commented, connections, people + content search (who posted about a topic, with resolved permalinks)…