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 diillson/chatcli --skill web-researchgit clone --depth 1 https://github.com/diillson/chatcliWrote 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/diillson/chatcli/web-research)<a href="https://agentmods.dev/skills/diillson/chatcli/web-research"><img src="https://agentmods.dev/badge/skills/diillson/chatcli/web-research/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/diillson/chatcli/web-research"><img src="https://agentmods.dev/badge/skills/diillson/chatcli/web-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.00475 |
| Opus 5.5 | $0.00027 | $0.00190 |
| Sonnet 5.5 | $0.00013 | $0.00095 |
| Haiku 4.5 | $0.00007 | $0.00047 |
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 1mo 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
Web Research
Native, keyless deep research using ChatCLI's own tools — @websearch to discover sources and
@webfetch to read them. No third-party paid search middleman required; the configured search
chain handles providers.
Method (search → read → synthesize)
- Decompose the question into 2–4 sub-queries (different angles/keywords).
- Search each with
@websearch; collect the most relevant, recent, authoritative URLs. - Read the top sources with
@webfetch— don't answer from snippets alone; open the pages. - Cross-check any non-trivial claim against at least two independent sources. Flag conflicts.
- Synthesize a structured answer with inline citations (URL or source name per claim).
Quality bar
- Prefer primary sources (official docs, papers, vendor pages) over aggregators.
- Note publication dates; for "latest"/"current" questions, prefer the most recent.
- Distinguish fact from opinion/marketing. If sources disagree, say so and show both.
- If the web doesn't clearly answer it, say what's uncertain rather than guessing.
Output
End with a short Sources list (title + URL). Keep the body tight; lead with the answer, then the supporting detail.
When to escalate
For long-running monitoring ("watch this topic and tell me when X changes"), pair this skill
with @scheduler (periodic re-run) and @send (notify the user on their channel).
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.
- 1mo ago First seen · 48 lines · 67 tokens per session scan A e5af52a358f3
web-research is a skill published in the GitHub repository diillson/chatcli (93 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 475 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
agent-state-bar
A design guide for an agent status bar: a short, automatically updated summary of progress, remaining tasks, tool counts, errors, and system state placed near the latest model input.
context-engineering
A guide to organizing the instructions and information an AI agent receives at each step. It covers system prompts, tool descriptions, conversation history, on-demand skills, and protections against unsafe outside content.
kv-cache-design
A guide to arranging an AI agent's conversation so previously processed text can be reused. A KV cache stores intermediate results for earlier tokens, while a prompt cache reuses a stable beginning across requests.
loop-engineering
A guide to building reliable loops for AI agents that plan, act, check their work, and continue until a task is truly complete. It includes independent verification and a proposer-reviewer pattern in which one agent's work is checked using outside evidence.
reward-design
A guide to defining the scores that an AI agent receives during trial-and-error training. It covers checks based on rules, human preferences, or another model, and distinguishes rewarding the final result from rewarding the steps taken.
pptx
A guide for turning a paper, outline, or structured text into a PowerPoint presentation. It covers an 8–12-slide structure, concise slide points, and generation of a .pptx file.