web-cap: Instructions file for Codex

AGENTS.md

web-cap AGENTS.md is an instructions file for Codex, OpenCode from edgestorage/web-cap. It costs 414 tokens per session, scanned A, original, Apache-2.0.

A set of project instructions for releasing beta versions of the web-cap package. A beta version is a pre-release build used for testing before a regular release.

In plain words
What is it for?
Use it when preparing an npm beta release to check existing versions, commit code changes first, create an isolated release worktree, and update the package version there.
Why use it?
It prevents the working branch’s package version from being changed prematurely and helps choose the next beta number from published and private tags. It also keeps release-only version changes isolated in a temporary worktree.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is edgestorage/web-cap's own configuration. It tells Codex and OpenCode how to work on web-cap itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything web-cap configures →

Reuse

Borrowing it

Nothing to install: this file belongs to edgestorage/web-cap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/edgestorage/web-cap/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/edgestorage/web-cap

Made for: Codex, OpenCode.

Wrote 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.

agentmods badge for web-cap AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/edgestorage/web-cap/agents-md/github.svg)](https://agentmods.dev/instructions/edgestorage/web-cap/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/edgestorage/web-cap/agents-md"><img src="https://agentmods.dev/badge/instructions/edgestorage/web-cap/agents-md/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.

agentmods 80×15 button for web-cap AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/edgestorage/web-cap/agents-md"><img src="https://agentmods.dev/badge/instructions/edgestorage/web-cap/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 414 This file is loaded in full into every session.
When invoked 414 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00414 $0.00414
Opus 5.5 $0.00166 $0.00166
Sonnet 5.5 $0.00083 $0.00083
Haiku 4.5 $0.00041 $0.00041

Measured 2mo ago against content hash 7784dadfddbc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

AGENTS.md · 27 lines

What it actually says

Agent Notes

Beta Release Flow

When asked to publish a beta version:

  1. Do not change package.json version on the current branch.
  2. Determine BASE_VERSION from the latest npm beta dist-tag, unless the user explicitly pins a different base version. Do not derive it from the current branch package.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, then BASE_VERSION=0.0.7 and the next beta is 0.0.7-beta.4.
  3. 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.*"
  4. Commit any requested code changes on the current branch first, without changing the package version.
  5. Create a temporary release worktree from the current HEAD.
    • Example: git worktree add /private/tmp/web-cap-tag-${BASE_VERSION}-beta.N HEAD
  6. In that temporary worktree only, update package.json to the beta version.
  7. Commit the release version change in the temporary worktree.
    • Example: chore: release ${BASE_VERSION}-beta.N
  8. Create v${BASE_VERSION}-beta.N on that temporary release commit.
  9. Push only the tag to the private remote.
    • Example: git push private v${BASE_VERSION}-beta.N
  10. Verify:
  • git show v${BASE_VERSION}-beta.N:package.json reports the beta version.
  • The current branch package.json still has its original version.
  • The current branch worktree is clean.
Changes

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.

  1. 2mo ago First seen · 27 lines · 414 tokens per session scan A 7784dadfddbc

Subscribe to this mod's changes

web-cap AGENTS.md is an instructions file published in the GitHub repository edgestorage/web-cap (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 414 tokens to every session, about $0.0017 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-08-30.

Related

web-cap AGENTS.md compared with instructions from other repositories

web-cap AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
web-cap AGENTS.mdedgestorage/web-capInstructions file114mo agoApache-2.0A414Codex, OpenCode
skill-doctor github-automation.instructions.mdevilstar2016/skill-doctorInstructions file168d agoMITA72GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot