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/web4-org/web4/agents-mdgit clone --depth 1 https://github.com/web4-org/web4What 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.00575 | $0.00575 |
| Opus 5 | $0.00287 | $0.00287 |
| Sonnet 5 | $0.00115 | $0.00115 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
web4 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
This repository is a Rust workspace with two crates:
crates/web4-core: compiler/runtime logic, W4ML parsing, shared APIs.crates/web4-gateway: HTTP gateway binary and rendering/auth/policy handlers.
Supporting folders:
docs/: operational and conformance docs (RUNBOOK.md,CONFORMANCE-MATRIX.md).examples/: sample.w4documents and service stubs used for local testing.tests/: reserved top-level test space (currently minimal); most tests live per crate.config.json: local gateway runtime config.
Build, Test, and Development Commands
Use workspace-level Cargo commands from the repo root:
cargo check --workspace— fast compile check.cargo build --workspace— build all crates.cargo test --workspace— run unit + integration tests.cargo run -p web4-gateway -- config.json— start the gateway with explicit config.cargo fmt --allandcargo clippy --workspace --all-targets -- -D warnings— format and lint before PRs.
Coding Style & Naming Conventions
- Follow Rust 2021 defaults; use
rustfmtoutput as the style source of truth. - Use
snake_casefor files, modules, and functions;PascalCasefor types/traits;SCREAMING_SNAKE_CASEfor constants. - Keep modules focused (e.g., gateway logic is split under
src/logic/). - Prefer explicit error types (
thiserror) over stringly typed errors.
Testing Guidelines
- Do not place tests inside main feature/logic source files; keep tests in
tests/directories to separate behavior validation from production code. - Add integration tests under each crate’s
tests/directory (examples:runtime_flow.rs,path_safety.rs). - Keep test names behavior-focused (
rejects_invalid_schema,serves_default_template). - For parser/runtime changes, include success + failure-path coverage.
- Run
cargo test --workspacelocally before opening a PR.
Commit & Pull Request Guidelines
Git history is not available in this checkout, so follow Conventional Commits (feat:, fix:, chore:, test:) in imperative mood.
For PRs, include:
- scope and motivation,
- linked issue(s) or task reference,
- test evidence (command + result),
- sample request/response or screenshot when gateway behavior 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.
- 2d ago First seen · 46 lines · 575 tokens per session scan A 5a34f80418c3
web4 AGENTS.md is an instructions file published in the GitHub repository web4-org/web4 (23 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 575 tokens to every session, about $0.0029 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.