web4: Instructions file for Codex

AGENTS.md

web4 AGENTS.md is an instructions file for Codex, OpenCode from web4-org/web4. It costs 575 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for web4, a Rust workspace containing a core compiler/runtime and an HTTP gateway. A workspace is one project that contains multiple related Rust packages.

In plain words
What is it for?
Use them when building, testing, formatting, linting, or modifying the web4-core and web4-gateway packages.
Why use it?
They explain the project layout, development commands, coding conventions, and checks expected before submitting changes.

Instructions file for CodexOpenCode

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

This is web4-org/web4's own configuration. It tells Codex and OpenCode how to work on web4 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 web4 configures →

Reuse

Borrowing it

Nothing to install: this file belongs to web4-org/web4. 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/web4-org/web4/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/web4-org/web4

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 web4 AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/web4-org/web4/agents-md"><img src="https://agentmods.dev/badge/instructions/web4-org/web4/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 575 This file is loaded in full into every session.
When invoked 575 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.00575 $0.00575
Opus 5.5 $0.00230 $0.00230
Sonnet 5.5 $0.00115 $0.00115
Haiku 4.5 $0.00057 $0.00057

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

Security

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 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 · 46 lines

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 .w4 documents 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 --all and cargo clippy --workspace --all-targets -- -D warnings — format and lint before PRs.

Coding Style & Naming Conventions

  • Follow Rust 2021 defaults; use rustfmt output as the style source of truth.
  • Use snake_case for files, modules, and functions; PascalCase for types/traits; SCREAMING_SNAKE_CASE for 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 --workspace locally 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.

Read the full file on GitHub · 46 lines

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 · 46 lines · 575 tokens per session scan A 5a34f80418c3

Subscribe to this mod's changes

web4 AGENTS.md is an instructions file published in the GitHub repository web4-org/web4 (23 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 575 tokens to every session, about $0.0023 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

web4 AGENTS.md compared with instructions from other repositories

web4 AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
web4 AGENTS.mdweb4-org/web4Instructions file238mo agoApache-2.0A575Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot