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/html-to-markdown --skill e2e-fixturesgit 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/e2e-fixtures)<a href="https://agentmods.dev/skills/xberg-io/html-to-markdown/e2e-fixtures"><img src="https://agentmods.dev/badge/skills/xberg-io/html-to-markdown/e2e-fixtures/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/html-to-markdown/e2e-fixtures"><img src="https://agentmods.dev/badge/skills/xberg-io/html-to-markdown/e2e-fixtures.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.00046 | $0.00299 |
| Opus 5.5 | $0.00018 | $0.00120 |
| Sonnet 5.5 | $0.00009 | $0.00060 |
| Haiku 4.5 | $0.00005 | $0.00030 |
Grade A, and why
e2e-fixtures 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 2d 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 E2E Fixtures
- Each file under
fixtures/<topic>/holds a JSON array of fixtures; the directory is the topic and matchesdocs.topic. Topics:conversion,options,metadata,visitor,edge-cases,structure,result,real-world,smoke. There is nocategoryorskipfield in practice. - Fields:
id,description,docs {topic, stem, title},input,assertions, andvisitorfor visitor fixtures. - Every fixture runs the single call
convert(html, options):input.htmlis the document,input.optionsan optionalConversionOptionsobject. - Assertion types in use:
contains_all,contains,not_contains,not_empty,equals,count_min,count_equals. Most assert oncontent.
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.
- 2d ago First seen · 21 lines · 46 tokens per session scan A 71f567401811
e2e-fixtures is a skill published in the GitHub repository xberg-io/html-to-markdown (886 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 299 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-28.
Other skills, from other repositories
e2e-fixtures
One JSON object per file under fixtures/ /. The directory is the default category; an explicit category field overrides it and names the generated test file (e.g. fixtures/pluginapi/listrerankerbackends.json sets rerankerbackendmanagement, so its Python test lands in e2e/python/tests/testrerankerbackendmanagement.py).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
AI System Quality Engineer
Test LLM, RAG, MCP, and agentic systems end to end. Build golden datasets, run deterministic checks and LLM judges, score retrieval, probe prompt injection, verify tool use, and gate CI on thresholds. Orchestrates DeepEval, Ragas, promptfoo, and Langfuse.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…