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/microsoft/wassette/agents-mdgit clone --depth 1 https://github.com/microsoft/wassetteWhat 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.00476 | $0.00476 |
| Opus 5 | $0.00238 | $0.00238 |
| Sonnet 5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
wassette 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guide for Wassette
Wassette is an MCP server that runs tools as WebAssembly components with Wasmtime. This file is the entry point for coding agents and contributors; the linked documentation and skills are the canonical sources for detailed guidance.
Start here
- Contributing: contribution requirements and release-note policy.
- Developer guide: prerequisites, repository layout, build, test, lint, documentation, and local CI workflows.
- Architecture: system design and component boundaries.
- Release process: release automation and versioning.
Agent skills
Focused workflows live under .agents/skills/:
| Skill | Use it for |
|---|---|
build-and-test |
Building the workspace, examples, and test components |
rust-code-style |
Rust design, formatting, Clippy, and dependency checks |
copyright-headers |
Applying the required headers to Rust files |
mcp-inspector-testing |
Testing server behavior through MCP Inspector |
documentation |
Writing, building, and previewing the mdBook |
pull-request |
Writing concise, user-facing pull requests |
Agents that support the Agent Skills standard should invoke the relevant skill.
Other agents should read its SKILL.md before performing that workflow.
Repository requirements
- Prefer the repository
justrecipes over ad-hoc commands; several recipes build required WebAssembly components before the Rust workspace. - Format Rust with
cargo +nightly fmt, lint withcargo clippy --workspace, and check unused dependencies withcargo machete. - Every Rust source file must begin with the Microsoft copyright header; use
./scripts/copyright.sh. - Validate server-facing behavior with MCP Inspector when the change affects MCP tools, resources, prompts, transports, or runtime behavior.
- Release notes are generated from pull request titles. Write a clear,
user-facing title; do not create or update a
CHANGELOG.md.
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 · 50 lines · 476 tokens per session scan A b3059fb6d6fc
wassette AGENTS.md is an instructions file published in the GitHub repository microsoft/wassette (938 stars, last pushed 4d ago), licensed MIT. It adds 476 tokens to every session, about $0.0024 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
cri-o AGENTS.md
AGENTS.md instructions for cri-o/cri-o, covering cri-o project context for ai agents, project overview, critical workflow rules (from user's preferences), repository structure and build system.
cri-o CLAUDE.md
Claude Code instructions for cri-o/cri-o: See AGENTS.md for detailed project context and workflow instructions.
hyper-mcp AGENTS.md
AGENTS.md instructions for hyper-mcp-rs/hyper-mcp, covering agents.md, project overview, tooling, commits and testing.
traverse CLAUDE.md
Instructions for traverse-framework/traverse, covering traverse development guidelines, governance, active technologies, project structure and commands.
traverse AGENTS.md
Instructions for traverse-framework/traverse, covering traverse — agent coordination, agent coordination, 1. check for claude code claim, 2. check for claude code branch and 3. claim the ticket (only if pre-flight passes).
Dippy CLAUDE.md
Instructions for ldayton/Dippy, a project described as: 🐤 Less permission fatigue, more momentum. Dippy knows what’s safe to run and keeps Claude on track when plans change.