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/broxy-dev/www/agents-mdgit clone --depth 1 https://github.com/broxy-dev/wwwWhat 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.01376 | $0.01376 |
| Opus 5 | $0.00688 | $0.00688 |
| Sonnet 5 | $0.00275 | $0.00275 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
www 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 185 lines · 1,376 tokens per session scan A bb7f1c408f4d
www AGENTS.md is an instructions file published in the GitHub repository broxy-dev/www (4 stars, last pushed 5mo ago), with no licence file. It adds 1,376 tokens to every session, about $0.0069 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 instructions, from other repositories
actual-mcp-server copilot-instructions.md
Instructions for agigante80/actual-mcp-server, covering copilot instructions for actual mcp server, project overview, architecture essentials, critical pattern: withactualapi wrapper and tool structure.
actual-mcp-server unit-tests.instructions.md
Instructions for agigante80/actual-mcp-server, covering rules for unit test files (tests/unit/), generatedtools.smoke.test.js, schemavalidation.test.js and general.
actual-mcp-server tool-files.instructions.md
Instructions for agigante80/actual-mcp-server: (prints every @actual-app/api method against the current tool list; read-only, safe to run).
actual-mcp-server playwright-tests.instructions.md
Instructions for agigante80/actual-mcp-server, covering rules for playwright e2e test files (tests/e2e/) and config files.
actual-mcp-server integration-tests.instructions.md
Instructions for agigante80/actual-mcp-server: Read tests/manual/README.md Technical Guidelines before editing any file here.
webmcpify AGENTS.md
Instructions for TueJon/webmcpify: This repository IS an agent skill. If a user asked you to "webmcpify" a project or make it agent-ready with WebMCP, do not explore this repo further — read and follow skills/webmcpify/SKILL.md inside the target project's working directory.