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/xberg-io/html-to-markdown/apinpx skills add xberg-io/html-to-markdown --skill apigit clone --depth 1 https://github.com/xberg-io/html-to-markdownWrote 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/html-to-markdown/api)<a href="https://agentmods.dev/skills/xberg-io/html-to-markdown/api"><img src="https://agentmods.dev/badge/skills/xberg-io/html-to-markdown/api.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.00013 | $0.00358 |
| Opus 5 | $0.00006 | $0.00179 |
| Sonnet 5 | $0.00003 | $0.00072 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
api 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.
What it actually says
html-to-markdown-rs API Reference
Use this skill when working with html-to-markdown-rs generated language APIs, data types, configuration, or error surfaces.
Generated reference pages:
- docs-site/src/content/docs/reference/api-python.md
- docs-site/src/content/docs/reference/api-typescript.md
- docs-site/src/content/docs/reference/api-ruby.md
- docs-site/src/content/docs/reference/api-php.md
- docs-site/src/content/docs/reference/api-c.md
- docs-site/src/content/docs/reference/api-go.md
- docs-site/src/content/docs/reference/api-java.md
- docs-site/src/content/docs/reference/api-csharp.md
- docs-site/src/content/docs/reference/api-elixir.md
- docs-site/src/content/docs/reference/api-wasm.md
- docs-site/src/content/docs/reference/api-r.md
- docs-site/src/content/docs/reference/api-kotlin-android.md
- docs-site/src/content/docs/reference/api-swift.md
- docs-site/src/content/docs/reference/api-dart.md
- docs-site/src/content/docs/reference/api-zig.md
- docs-site/src/content/docs/reference/api-rust.md
- docs-site/src/content/docs/reference/configuration.md
- docs-site/src/content/docs/reference/types.md
- docs-site/src/content/docs/reference/errors.md
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 · 36 lines · 13 tokens per session scan A 0fc8e473bb4e
api is a skill published in the GitHub repository xberg-io/html-to-markdown (860 stars, last pushed 5d ago), licensed MIT. It adds 13 tokens to every session and 358 once invoked, about $0.0001 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
xberg
Extract text, tables, metadata, and images from 107 document formats (PDF, Office, images, HTML, email, archives, academic) using Xberg. Use when writing code that calls Xberg APIs in Python, Node.js/TypeScript, Rust, or CLI. Covers installation, extraction (sync/async), configuration (OCR, chunking, output format)…
plugin-architecture-patterns
Design, implement, or diagnose Xberg plugin traits, typed registries, priority collisions, lifecycle, native extractors, and Alef-generated Python plugin bridges. Load for plugin-system work, not ordinary extractor parsing.
extracting-keywords
Use when extracting keywords (YAKE/RAKE) from documents — and, secondarily, when detecting document language or generating embeddings for RAG and search. Covers the keyword config (and its feature gating), --detect-language, and the standalone embed command with real flags.
chunking-embeddings
Chunking, embeddings, and RAG pipeline integration.
batch-extraction
Use when extracting from many files at once with shared config, bounded parallelism, per-file overrides, and error recovery. Covers the batch command, --file-configs, --max-concurrent, and output layout.
chunking
Use when splitting extracted text into chunks for LLM context windows or RAG ingestion. Covers chunk size, overlap, markdown/yaml/semantic chunkers, tokenizer-based sizing, and the standalone chunk command.