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/yohn1985/jarvisbot/webnpx skills add yohn1985/jarvisbot --skill webgit clone --depth 1 https://github.com/yohn1985/jarvisbotWhat 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.00032 | $0.00309 |
| Opus 5 | $0.00016 | $0.00154 |
| Sonnet 5 | $0.00006 | $0.00062 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
web scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
tools: urllib (HTTP), DuckDuckGo HTML, the LLM router What it actually says
web
Gives Jarvis eyes on the live internet so it can check reality instead of guessing from stale training data (e.g. "is Ubuntu 26.04 out yet?").
fetch <url> readable text of a page
search <query> top results (title + url), DuckDuckGo, no API key
research <question> search -> fetch top results -> the brain answers from CURRENT info, with sources
Degrade-safe: any network/parse failure returns empty rather than crashing. The research answer is
instructed to trust the fetched results over training data and to cite source URLs.
Usage
./install.sh skill run web search "ubuntu 26.04 release date"
./install.sh skill run web research "is ubuntu 26.04 released and what's new"
./install.sh skill run web fetch https://example.com
What ships with it
2 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.
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 · 30 lines · 32 tokens per session scan A 7129679573a2
web is a skill published in the GitHub repository yohn1985/jarvisbot (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 309 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
agent-ready-features
This skill documents all agent-ready features published by Rise of Machine (https://riseofmachine.com) for automated discovery and integration.
browse-ai-tools
Use the Rise of Machine AI tools directory to discover curated AI tools for founders and SMBs, organised by category.
docs-writer
Draft or rewrite Strands Agents documentation pages. Use when writing new doc pages, rewriting pages that failed audit, drafting sections for existing pages, or writing blog posts and release notes about Strands. Also triggers on "write a doc", "draft a page", "rewrite the quickstart", "add a tutorial for X"…
design-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
research-repository
Build a repository that makes findings findable, reusable, and cumulative across teams. Use when the same research keeps getting redone. For synthesising one study, use affinity-diagram.
version-control-strategy
Define version control for design files, components, and libraries — branching, naming, and release. Use when file history is chaotic. For design system contribution rules, use design-system-governance (design-systems).