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 xberg-io/crawlberg --skill crawl-engine-mapgit clone --depth 1 https://github.com/xberg-io/crawlbergWrote 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/xberg-io/crawlberg/crawl-engine-map)<a href="https://agentmods.dev/skills/xberg-io/crawlberg/crawl-engine-map"><img src="https://agentmods.dev/badge/skills/xberg-io/crawlberg/crawl-engine-map/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/xberg-io/crawlberg/crawl-engine-map"><img src="https://agentmods.dev/badge/skills/xberg-io/crawlberg/crawl-engine-map.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.00048 | $0.00537 |
| Opus 5.5 | $0.00019 | $0.00215 |
| Sonnet 5.5 | $0.00010 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
crawl-engine-map 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 yesterday.
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.
What it actually says
Paths are relative to crates/crawlberg/src/.
- Crawl engine:
engine/—crawl_loop.rs(main loop),builder.rs(configuration),batch.rs(batch crawling); it drives the URL frontier, fetching and extraction. - HTTP:
http.rs; robots.txt viarobots.rs, sitemap discovery viasitemap.rs. - Tower layers in
tower/:rate_limit.rs,cache.rs,ua_rotation.rs,tracing_layer.rs. - HTML pipeline: parse with
tl, thenpruning.rs,normalize.rs,markdown.rs(viahtml-to-markdown-rs). Extraction inhtml/(links, metadata, JSON-LD, feeds, images). - Entry points:
scrape.rs(single page),map.rs(URL discovery). WAF detection:waf/. browserfeature: chromiumoxide inbrowser.rs,browser_pool.rs,browser_profile.rs,browser_detect.rs; page actions ininteract/; fingerprint patches instealth.rs; SSRF re-validation of browser requests inssrf_intercept.rs/ssrf_intercept/.browser-nativefeature:native_browser.rsvia thecrawlberg-browsercrate.aifeature:research/(agent.rs,planner.rs,synthesizer.rs) usingliter-llmandminijinjaprompt templates.mcpfeature:mcp/exposes crawling as tool calls.apifeature:api/serves HTTP endpoints via axum.warcfeature:warc.rs.- Types:
types/config.rs,types/results.rs,types/discovery.rs,types/metadata.rs. - Crawling logic stays in the Rust core; binding crates (
crates/crawlberg-{py,node,php,wasm,ffi,jni}, sharedcrawlberg-bindings-common) andcrawlberg-cliare thin wrappers.
What ships with it
1 file 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.
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.
- yesterday Changed · +2 lines e336fe201475
- 2d ago First seen · 25 lines · 48 tokens per session scan A 39d6d28182ed
crawl-engine-map is a skill published in the GitHub repository xberg-io/crawlberg (192 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 537 once invoked, about $0.0002 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-10-27.
Other skills, from other repositories
tree-sitter-language-pack-extracting-code-structure
Use when the user wants structured code metadata from a source file — functions, classes, imports, exports, symbols, docstrings, comments, or syntax diagnostics. Covers ts-pack process feature flags, the JSON result shape, and the default feature set.
tree-sitter-language-pack-chunking-for-llms
Use when the user wants to split source code into chunks for an LLM context window without breaking syntax mid-construct. Covers ts-pack process --chunk-size, why syntax-aware splits beat fixed-byte splits, picking a size, and the chunk JSON shape.
tree-sitter-language-pack-detecting-languages
Use when the user wants to know which programming language a file or snippet is. Covers implicit detection in ts-pack parse/process, confirming support with ts-pack list/info, and the SDK detection functions for path, extension, and raw content.
tree-sitter-language-pack-managing-parsers
Use when the user needs to manage the tree-sitter parser cache — prefetch parsers for offline or CI runs, list what is downloaded, inspect a language, find the cache directory, or clean it. Covers ts-pack download, list, info, cache-dir, clean, and init.
tree-sitter-language-pack-parsing-source
Use when the user wants a tree-sitter syntax tree for a source file — an s-expression dump or JSON tree. Covers ts-pack parse, language auto-detection vs --language, stdin input, and reading haserrors.
tree-sitter-language-pack-using-the-mcp-server
Use when parsing source, extracting code structure, or detecting a language through the tree-sitter-language-pack MCP server's tools, rather than shelling out to the ts-pack CLI. Covers the tool surface, the auto-installing launcher, and when MCP beats the CLI or SDK.