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/forest/agent-skills/web-clinpx skills add forest/agent-skills --skill web-cligit clone --depth 1 https://github.com/forest/agent-skillsWhat 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.00138 | $0.01061 |
| Opus 5 | $0.00069 | $0.00531 |
| Sonnet 5 | $0.00028 | $0.00212 |
| Haiku 4.5 | $0.00014 | $0.00106 |
Grade A, and why
web-cli 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 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.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Browser Tool
You have the ability to browse the web with a full browser via the system shell.
Always use the built-in bash CLI tool web to interact with and test web apps as you build features.
This should be your GO-TO TOOL for verifying functionality, build status, etc.
Basic Usage
web <url> [options]
By default the page is converted to markdown and displayed to stdout:
web example.com
web localhost:4000/dashboard
You can redirect output to a file:
web example.com --raw > output.html
web example.com --raw > output.json
Never pass --raw or --truncate-after unless the user asks, or if it makes sense (e.g., fetching JSON from an API).
Options
| Option | Description |
|---|---|
--raw |
Output raw HTML/JSON instead of markdown |
--truncate-after <n> |
Truncate after n characters (default: 100000) |
--screenshot <path> |
Save screenshot to filepath |
--profile <name> |
Use named session profile (default: "default") |
--js <code> |
Execute JavaScript after page loads |
--form <id> |
Target form by ID for submission |
--input <name> |
Field name to fill (repeatable) |
--value <value> |
Value for preceding --input |
--after-submit <url> |
URL to load after form submission |
Session Persistence
Each invocation of web uses a shared session — cookie sessions and other state are preserved across separate invocations. This means you can log in to a site and then issue another web command to view or interact with a logged-in page.
Use the optional --profile argument to browse under unique profiles, which is useful for testing multiple logins or sessions:
web http://localhost:4000 --profile "user1"
web http://localhost:4000 --profile "user2"
Common Patterns
Verify a Page Works
web localhost:4000/users
Authenticated Session
# 1. Login and establish session
web localhost:4000/login \
--form login_form \
--input email --value [email protected] \
--input password --value secret \
--profile app_session
# 2. Access protected pages with same session
web localhost:4000/dashboard --profile app_session
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 · 140 lines · 138 tokens per session scan A 28a46eb9cecc
web-cli is a skill published in the GitHub repository forest/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 138 tokens to every session and 1,061 once invoked, about $0.0007 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
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
mintlify-preview
Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".