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/runxhq/runx/extractnpx skills add runxhq/runx --skill extractgit clone --depth 1 https://github.com/runxhq/runxWrote 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/runxhq/runx/extract)<a href="https://agentmods.dev/skills/runxhq/runx/extract"><img src="https://agentmods.dev/badge/skills/runxhq/runx/extract.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.00018 | $0.01309 |
| Opus 5 | $0.00009 | $0.00655 |
| Sonnet 5 | $0.00004 | $0.00262 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
extract 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Extract
What this skill does
Extract structured JSON from a bounded HTML or plain-text source inside the
skill package, validate the result against a declared JSON Schema, and emit a
digest-bound provenance packet. The runner is deterministic: it reads local
fixture bytes, extracts headings, useful paragraphs, and HTTP/API terms, checks
the packet against packets/extraction.schema.json, and returns
runx.structured_extraction.result.v1.
This is not a scraper or crawler. Network fetch belongs in a separate governed web-fetch step. This skill starts after the bytes are already available as an approved package fixture, so the runx receipt can bind the input digest, schema digest, and validated output digest without depending on a live website.
When to use this skill
Use this skill when an agent needs a reproducible extraction packet from messy reference material, docs snapshots, benchmark fixtures, or captured public web content. It is appropriate when the source bytes have already been fetched, approved for local use, and pinned inside the skill package.
Use it as the extraction stage in a larger chain: fetch or curate bytes first, run structured extraction second, then pass the validated packet to a downstream agent, reviewer, search index, or evidence bundle.
When not to use this skill
Do not use this skill to fetch URLs, bypass network policy, process private customer data, parse credentials, or summarize a source without a schema. Do not use it when the desired output is free-form prose; this runner exists to produce typed, schema-checked JSON.
If the source bytes are not already present, stop with needs_input and use a
web-fetch or repository-read skill with its own authority grant and receipt. If
the schema is missing or unknown, stop with needs_more_evidence instead of
inventing a packet shape.
Procedure
- Resolve
input_pathandschema_pathrelative to the skill package. - Reject any path that escapes the package root.
- Read the source bytes and JSON Schema bytes.
- Record SHA-256 digests for both inputs.
- Extract a bounded set of headings, paragraphs, and HTTP/API terms.
- Build
runx.structured_extraction.result.v1. - Validate the packet against the schema and deterministic internal checks.
- Return the packet only when validation passes; otherwise fail closed.
What ships with it
8 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.
- fixtures/rfc9110-http-semantics.html 1165 KB
- fixtures/rfc9110-http-semantics.yaml 1.7 KB
- package.json 198 B
- packets/extraction.schema.json 5.8 KB
- tools/structured/extract/fixtures/rfc9110.yaml 797 B
- tools/structured/extract/manifest.json 1.2 KB
- tools/structured/extract/run.mjs 14 KB runs code
- X.yaml 1.8 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.
- yesterday First seen · 158 lines · 18 tokens per session scan A 5e4b7c095b71
extract is a skill published in the GitHub repository runxhq/runx (84 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 1,309 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-09-03.
Other skills, from other repositories
morph-ppt
Generate Morph-animated PPTs with officecli.
dynamic-resources
Example skill loaded from resourcesdiscover.
officecli-pptx
Use this skill any time a .pptx file is involved -- as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file; editing, modifying, or updating existing presentations; combining or splitting slide files; working with…
officecli-financial-model
Use this skill when the user wants to build a financial model, 3-statement model, DCF valuation, cap table, scenario analysis, or financial projections in Excel. Trigger on: 'financial model', '3-statement model', 'DCF', 'cap table', 'pro forma', 'projections', 'sensitivity analysis', 'waterfall', 'debt schedule'…
officecli-docx
Use this skill any time a .docx file is involved -- as input, output, or both. This includes: creating Word documents, reports, letters, memos, or proposals; reading, parsing, or extracting text from any .docx file; editing, modifying, or updating existing documents; working with templates, tracked changes, comments…
officecli-xlsx
Use this skill any time a .xlsx file is involved -- as input, output, or both. This includes: creating spreadsheets, financial models, dashboards, or trackers; reading, parsing, or extracting data from any .xlsx file; editing, modifying, or updating existing workbooks; working with formulas, charts, pivot tables, or…