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 instructions/edgestorage/web-cap/agents-mdgit clone --depth 1 https://github.com/edgestorage/web-capWhat 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.00414 | $0.00414 |
| Opus 5 | $0.00207 | $0.00207 |
| Sonnet 5 | $0.00083 | $0.00083 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
web-cap AGENTS.md 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 2d 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
Agent Notes
Beta Release Flow
When asked to publish a beta version:
- Do not change
package.jsonversion on the current branch. - Determine
BASE_VERSIONfrom the latest npm beta dist-tag, unless the user explicitly pins a different base version. Do not derive it from the current branchpackage.json.- npm beta:
npm_config_cache=/private/tmp/web-cap-npm-cache npm view web-capability@beta version - Example: if npm beta is
0.0.7-beta.3, thenBASE_VERSION=0.0.7and the next beta is0.0.7-beta.4.
- npm beta:
- Check existing beta versions from both npm and the private git remote, then choose the next beta number for that
BASE_VERSION.- npm:
npm_config_cache=/private/tmp/web-cap-npm-cache npm view web-capability versions --json - private tags:
git ls-remote --tags private "v${BASE_VERSION}-beta.*"
- npm:
- Commit any requested code changes on the current branch first, without changing the package version.
- Create a temporary release worktree from the current
HEAD.- Example:
git worktree add /private/tmp/web-cap-tag-${BASE_VERSION}-beta.N HEAD
- Example:
- In that temporary worktree only, update
package.jsonto the beta version. - Commit the release version change in the temporary worktree.
- Example:
chore: release ${BASE_VERSION}-beta.N
- Example:
- Create
v${BASE_VERSION}-beta.Non that temporary release commit. - Push only the tag to the
privateremote.- Example:
git push private v${BASE_VERSION}-beta.N
- Example:
- Verify:
git show v${BASE_VERSION}-beta.N:package.jsonreports the beta version.- The current branch
package.jsonstill has its original version. - The current branch worktree is clean.
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.
- 2d ago First seen · 27 lines · 414 tokens per session scan A 7784dadfddbc
web-cap AGENTS.md is an instructions file published in the GitHub repository edgestorage/web-cap (11 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 414 tokens to every session, about $0.0021 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-30.
Other instructions, from other repositories
browser-bridge AGENTS.md
Instructions for koltyakov/browser-bridge, covering project guide, data flow, package map, where to find things and method dispatch (extension side).
opentabs AGENTS.md
Instructions for opentabs-dev/opentabs, covering project instructions for codex, project overview, architecture, you are connected to this project's mcp server and workflow skills.
codex-browser-bridge AGENTS.md
Instructions for DeliciousBuding/codex-browser-bridge, covering agents.md, 仓库级 skill, mcp 工具设计规范, 1. browser 层（src/browser.rs） and 2. mcp 层（src/mcp/ 目录）.
chromeboost GEMINI.md
Instructions for lordamdal/chromeboost, covering chromeboost — gemini instructions, what chromeboost is, when to use chromeboost (be proactive), hard rules — never break these and standard flow pattern.
chromeboost CLAUDE.md
Instructions for lordamdal/chromeboost, covering chromeboost — repo-developer guide, what chromeboost is, repository layout, development commands and tests/antibot/ (run locally; not in ci).
browser-agent AGENTS.md
Instructions for uiuing/browser-agent, covering agents.md — guide for ai coding agents, setup & commands, tests — run these before claiming done, repository layout and architecture invariants (do not break these).