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/ytvee-dev/webdev-agent-kit/agents-mdgit clone --depth 1 https://github.com/ytvee-dev/webdev-agent-kitWhat 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.01336 | $0.01336 |
| Opus 5 | $0.00668 | $0.00668 |
| Sonnet 5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
webdev-agent-kit 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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WebDev Agent Kit Runtime Policy
Purpose
This is the compact runtime entrypoint for the .agents bundle. It routes work to client-neutral core policy, an evidence-gated profile, verified project facts, and the smallest matching skill. Detailed rules stay in their owning common/** or skill reference and are loaded only when relevant.
Bundle paths are rooted at .agents. Generated dist/** output is never source truth. The host-root instruction pointer is managed only by project-onboarding-adapter with explicit approval; ordinary bundle work must not replace it.
Precedence And Approvals
Resolve conflicts through common/policy-precedence.md: system, client security, and sandbox restrictions; current user request; confirmed scope and approvals; host-project instructions; verified project/** facts; selected skill; active profile; generic defaults.
Require explicit approval before installing packages or tools, changing configuration outside scope, adding test infrastructure, replacing project instructions, performing irreversible actions, or contacting external people or systems. New tests require an explicit current request; relevant existing-test maintenance follows common/test-policy.md.
README.md may be read only when relevant under common/readme-policy.md, never as sole technical evidence or runtime authority. Reading never authorizes editing. Do not create or change an existing README unless the current user explicitly requests that README change.
Context Loading And Workflow Scale
Classify before reading broadly:
Fast Lookup: narrow question, file location, or code explanation; search and read only decisive snippets.Lightweight Workflow: one obvious, low-risk local change; avoid planning and toolchain overhead.Standard Workflow: multi-file work, unclear root cause, refactor boundary, or bounded verification.Deep Workflow: new project, architecture or migration, broad redesign, repeated failure, or resumable work.
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.
- yesterday First seen · 82 lines · 1,336 tokens per session scan A fd6275987bac
webdev-agent-kit AGENTS.md is an instructions file published in the GitHub repository ytvee-dev/webdev-agent-kit (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,336 tokens to every session, about $0.0067 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
skills AGENTS.md
Instructions for bitwise-media-group/skills, covering bitwise skills — repository conventions, layout, dual manifests (claude + codex), skill frontmatter policy and progressive disclosure.
harness-design CLAUDE.md
Instructions for zanwei/harness-design, covering claude.md, architecture, workflow, 5-pass verification and auxiliary skills.
skills CLAUDE.md
Instructions for bitwise-media-group/skills, a project described as: Coding agent marketplace for skills used by the BitWise Media Group.
claude-code-settings copilot-instructions.md
Instructions for feiskyer/claude-code-settings, covering claude.md, environment setup, required dependencies, configuration and skills.
cherry-studio AGENTS.md
AGENTS.md instructions for CherryHQ/cherry-studio, a project described as: AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs.
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.