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/vladkesler/initrunner/structured-extractionnpx skills add vladkesler/initrunner --skill structured-extractiongit clone --depth 1 https://github.com/vladkesler/initrunnerWrote 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/vladkesler/initrunner/structured-extraction)<a href="https://agentmods.dev/skills/vladkesler/initrunner/structured-extraction"><img src="https://agentmods.dev/badge/skills/vladkesler/initrunner/structured-extraction.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.00030 | $0.00902 |
| Opus 5 | $0.00015 | $0.00451 |
| Sonnet 5 | $0.00006 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade A, and why
structured-extraction 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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structured web data extraction skill.
When to activate
Use this skill when you need to:
- Extract specific data points from a web page (prices, features, specs)
- Build a comparison table from multiple pages or sites
- Scrape a list of items from a page (search results, product listings)
- Extract tabular data from a web page into a structured format
Methodology
1. Plan the extraction
Use the think tool to identify:
- What data points to extract (columns in your target table)
- Which pages contain the data (URLs or navigation paths)
- Whether the data is on one page or spread across multiple pages
- Whether pagination or interaction is needed to reveal the data
2. Navigate to the data
Open the target URL and confirm you landed on the right page:
open_url("https://example.com/pricing")
Check the title and URL in the response to verify.
3. Snapshot the page
Take a snapshot to understand the page structure:
snapshot()
Look for:
- Data containers (tables, cards, lists)
- Interactive elements that reveal more data (tabs, accordions, "Show more" buttons)
- Pagination controls
If the page has distinct sections, use a CSS selector to scope
the snapshot: snapshot(selector=".pricing-table")
4. Extract text content
Use get_text to pull text from specific elements or the full page:
get_text(ref="@e5") # specific element
get_text() # full page text
For tabular data, extracting the full page text often captures tables in a readable format.
5. Take evidence screenshots
Screenshot key pages for the research report:
screenshot(full_page=false) # viewport
screenshot(full_page=true) # full page
screenshot(annotate=true) # with element labels
Include screenshot paths in your report so the user can review the raw source.
6. Process with Python
Use Python to structure the extracted text into clean data:
data = [
{"name": "Plan A", "price": "$10/mo", "features": "5 users, 10GB"},
{"name": "Plan B", "price": "$25/mo", "features": "25 users, 100GB"},
]
# Format as markdown table
header = "| Plan | Price | Features |"
sep = "|------|-------|----------|"
rows = [f"| {d['name']} | {d['price']} | {d['features']} |" for d in data]
print(header)
print(sep)
print("\n".join(rows))
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.
- 3d ago First seen · 137 lines · 30 tokens per session scan A 3c1139c05fe5
structured-extraction is a skill published in the GitHub repository vladkesler/initrunner (41 stars, last pushed 5d ago), licensed Apache-2.0. It adds 30 tokens to every session and 902 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
hive.browser-automation
Required before any hive-browser CLI command. The browser is driven from the terminal by running hive-browser ... --json via terminalexec — not via MCP tools. Teaches the browser lifecycle rules (the bridge attaches to the USER'S running Chrome — never kill or launch browser processes; timeouts are transport issues…
hive.linkedin-automation
Read before automating LinkedIn with browser tools. LinkedIn combines shadow DOM (#interop-outlet), strict Trusted Types CSP that silently drops innerHTML, Lexical composer, native beforeunload dialogs that hang the bridge, and aggressive spam filters — each has bitten us at least once. Verified flows for profile…
hive.x-automation
Read before automating X / Twitter with browser tools. Verified flows for post, reply, delete, search-and-engage, plus the Draft.js compose quirks that silently disable the send button. Includes the daily-reply and job-market-reply playbooks. Requires hive.browser-automation for the underlying screenshot + coordinate…
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
hive.telegram-notifications-setup
Set up a Telegram notification channel (Sentinel) for a colony by driving the browser — create a bot via @BotFather in Telegram Web, store its token, detect the chat to notify, and turn Sentinel on so the colony can ping the user on Telegram and accept replies. Use when the user asks to "set up Telegram…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.