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/joinwell52-ai/codeflowmu-open/web-researchnpx skills add joinwell52-AI/CodeFlowMu-open --skill web-researchgit 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-research)<a href="https://agentmods.dev/skills/joinwell52-ai/codeflowmu-open/web-research"><img src="https://agentmods.dev/badge/skills/joinwell52-ai/codeflowmu-open/web-research.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.00067 | $0.00691 |
| Opus 5 | $0.00034 | $0.00345 |
| Sonnet 5 | $0.00013 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
web-research 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 5d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Research
Run an end-to-end research workflow by combining web-search and web-extract. Produce conclusions that remain traceable to the underlying webpages.
Workflow
- Define the research question, decision to support, scope, freshness requirement, and expected report shape.
- Use the
web-searchprocedure to construct queries and select authoritative, diverse sources. - Use the
web-extractprocedure on the selected URLs:- Open webpages.
- Use Playwright only for dynamic content when needed.
- Extract relevant正文.
- Extract relevant tables with headers and units.
- Preserve
source_urlon every evidence item. - Set explicit extraction quality gates; reject weak pages instead of treating navigation text as evidence.
- Compare sources. Resolve differences using source authority, dates, definitions, methods, and directness of evidence.
- Separate verified facts, reasonable inferences, conflicting evidence, and unknowns.
- Form conclusions only from extracted evidence. Attach one or more source URLs to each material claim.
- Write the requested answer or report with findings, evidence, limitations, and source list.
- When operating inside an agent task, use the available report tool and include source URLs in the report body or structured evidence.
- Do not generate a site-specific
.mjsprobe for normal work; configure the shared web tools instead. - When the research hierarchy is known, execute it in dependency order. Complete the inventory layer before sampling descendants, and continue automatically while each next step is read-only and in scope.
Research Report Contract
## Research Question
<question and scope>
## Method
<queries, source-selection rule, retrieval date, dynamic-page use>
## Findings
1. <finding> [source](source_url)
2. <finding> [source](source_url)
## Table Evidence
<normalized table or comparison, with source_url for each source/table>
## Conclusion
<answer, recommendation, or decision support>
## Uncertainty And Conflicts
<unknowns, stale data, conflicting definitions, inaccessible sources>
## Sources
- <title> - <source_url>
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.
- 5d ago First seen · 74 lines · 67 tokens per session scan A da2a41e02bc2
web-research is a skill published in the GitHub repository joinwell52-AI/CodeFlowMu-open (2 stars, last pushed 11d ago), licensed MIT. It adds 67 tokens to every session and 691 once invoked, about $0.0003 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-31.
Other skills, from other repositories
agentbro-release
Use when releasing AgentBro from this repository: merging dev/main, bumping versions, updating release notes, tagging, pushing, monitoring GitHub Actions, Homebrew cask publication, or fixing a bad release.
agentbro-pr-merge
Use when reviewing, fixing CI for, approving workflows for, or merging AgentBro pull requests into dev/main, especially external contributor PRs where contributor attribution matters.
source-command-check
跑全套本地校验(前端 lint/test/build + Rust check)。.
oculpm-journal
MCP 도구가 보이면 이 스킬 대신 도구를 쓴다 — journalwrite / planstatus / planupdate 가 경로·파일명·frontmatter 규격을 서버에서 보장한다. 아래는 도구가 없을 때 파일을 직접 쓰는 규격이다.
self-audit
작업을 "완료"라고 보고하기 직전, 스스로 결과를 감사할 때. 커밋/PR 직전 최종 점검에도 사용.
project-inception
Use when kicking off a new project or feature area in an ocul-pm tracked project (.oculpm/ present) — research the stack landscape via web search, then converse with the user (research-backed choices) to settle the optimal spec, and seed a discussion doc, a detailed 3-depth plan (plancreate), EVALS.md done-criteria…