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 joinwell52-AI/CodeFlowMu-open --skill web-extractgit clone --depth 1 https://github.com/joinwell52-AI/CodeFlowMu-openWrote 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/joinwell52-ai/codeflowmu-open/web-extract)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/web-extract"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/web-extract/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/joinwell52-ai/codeflowmu-open/web-extract"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/web-extract.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.00056 | $0.00774 |
| Opus 5.5 | $0.00022 | $0.00310 |
| Sonnet 5.5 | $0.00011 | $0.00155 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade A, and why
web-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 2mo 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Extract
Turn selected webpages into structured, traceable evidence. Preserve the source URL on every extracted item.
Workflow
- Open the exact selected URL. Record redirects and use the final canonical URL as
source_urlwhen known. - Inspect page title, publisher, publication or update date, and the content area relevant to the question.
- Prefer direct page reading or structured extraction for static pages.
- Use Playwright or an equivalent browser tool only when content requires JavaScript rendering, interaction, pagination, expansion, or scrolling.
- Extract only relevant正文 and preserve headings that give it meaning.
- Extract tables as structured rows and columns. Preserve headers, units, notes, and table captions.
- Separate page facts from interpretation. Keep exact short excerpts minimal and paraphrase the rest.
- Record extraction gaps such as login walls, robots restrictions, missing dates, truncated tables, or inaccessible content.
- Define acceptance before extraction. For dynamic pages, use
required_texts,min_content_chars,min_tables, ormin_structured_itemswithfail_on_quality=true. - Use
table_contains,max_tables, andmax_table_rowsto keep large comparison pages focused and model-consumable.
Output Contract
{
"source_url": "https://example.com/final-page",
"title": "page title",
"publisher": "source owner or null",
"published_at": "known date or null",
"retrieved_at": "retrieval timestamp",
"content": [
{
"heading": "section heading",
"text": "relevant extracted or faithfully paraphrased content",
"source_url": "https://example.com/final-page"
}
],
"tables": [
{
"caption": "table caption or null",
"columns": ["column A", "column B"],
"rows": [["value A", "value B"]],
"source_url": "https://example.com/final-page"
}
],
"extraction_notes": []
}
Dynamic Pages
- Use Playwright as a low-level extraction tool, not as the research methodology.
- Perform the minimum interaction required to reveal the relevant content.
- Prefer
wait_for_selectororwait_for_textover fixed sleeps. Useclick_textsandauto_scrollonly when required. - Request
screenshot_pathwhen visual evidence is part of acceptance. - Do not submit forms, log in, accept permissions, or trigger external side effects unless explicitly authorized.
- Record the interaction needed to obtain the content.
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.
- 2mo ago First seen · 69 lines · 56 tokens per session scan A 6b49b3b92b40
web-extract is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 774 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-08-31.
Other skills, from other repositories
dsh-record-browser-gif
A workflow for recording a real browser application as a GIF demonstration. It operates the running app, captures the interaction, encodes the frames, and checks the resulting file.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
ha-browser
Hope Agent browser automation — the standard status → tabs → snapshot → act loop, stale-ref recovery rules, and what to do when login / 2FA / captcha / camera-prompt / dialog blocks progress. Load this skill whenever you reach for the browser tool. Trigger on: user asks the agent to open / control / click / scrape /…
web-app-qa
Test a web app the way a real user would: click through the main flows, try odd inputs, watch for errors, and keep screenshots as proof. You get a bug report ranked by how serious each problem is.
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.
dsh-engineering
An engineering guide for implementing features, fixing bugs, and maintaining a project's AI engineering rules. It uses the project's existing code, callers, checks, documentation, and conventions rather than applying a generic template.