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 agentmods add skills/simota/agent-skills/trawlnpx skills add simota/agent-skills --skill trawlgit clone --depth 1 https://github.com/simota/agent-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/simota/agent-skills/trawl)<a href="https://agentmods.dev/skills/simota/agent-skills/trawl"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/trawl.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.05280 |
| Opus 5 | $0.00020 | $0.02640 |
| Sonnet 5 | $0.00008 | $0.01056 |
| Haiku 4.5 | $0.00004 | $0.00528 |
Grade A, and why
trawl 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 4d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Trawl
"Design the web that catches the web."
You are the crawl systems architect who designs how data is collected from the web at scale. You produce architecture specifications, frontier designs, and compliance frameworks — never execution code. You think in terms of URL frontiers, domain budgets, politeness contracts, and distributed worker fleets. Vector executes single-session scraping; you architect the systems that crawl millions of pages across thousands of domains.
Architecture determines crawl quality more than code does.
Compliance is not a filter — it is a load-bearing wall.
Every URL has a cost; every frontier needs persistence.
Scale parameters are not constraints — they are the design itself.
Principles: Architecture before execution · Compliance is structural, not optional · Scale parameters drive every decision · Frontier persistence prevents data loss · Design for the fleet, not the session
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- _common 10 B
- ARCHIVED_2026-08-20.md 1.2 KB
- reference/anti-detection-architecture.md 10.0 KB
- reference/autorun-schema.md 748 B
- reference/compliance-architecture.md 11 KB
- reference/crawl-monitoring.md 12 KB
- reference/dedup-strategies.md 10 KB
- reference/distributed-architecture.md 7.7 KB
- reference/extraction-pipeline-deep.md 11 KB
- reference/extraction-pipeline.md 7.8 KB
- reference/frontier-design.md 7.5 KB
- reference/handoffs.md 9.3 KB
- reference/link-graph.md 6.5 KB
- reference/observability.md 11 KB
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.
- 4d ago First seen · 325 lines · 40 tokens per session scan A 72baccb5f510
trawl is a skill published in the GitHub repository simota/agent-skills (75 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 5,280 once invoked, about $0.0002 per session on Opus 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
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
tutti-workspace-app-factory
Create, convert, or repair one Tutti workspace app as either a self-contained publishable package under package/ or a Chrome-style local debug app under .tutti/dev-app/. Use for mention://workspace-app-factory/create handoffs, mention://workspace-app-factory handoffs, standalone app generation, adapting existing…
seo-tech-audit
Judge the technical SEO facts produced by seo-crawl and return falsifiable findings + a health score. This is pure analysis — it does no network I/O and only reasons over the crawl JSON.
geo-score
Score how citable/ready a page is for AI answer engines, from crawl facts. Pure analysis — no network, no model calls. Deterministic so it is drift-comparable.
seo-content
Heuristic content/GEO-readiness analysis of the visible text from seo-crawl. No network. Judgments are heuristic (marked Estimated); raw counts are Measured.
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).