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 agents/microsoft/wassette/docsgit 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.00021 | $0.01526 |
| Opus 5 | $0.00010 | $0.00763 |
| Sonnet 5 | $0.00004 | $0.00305 |
| Haiku 4.5 | $0.00002 | $0.00153 |
Grade A, and why
Documentation Update Agent 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Update Agent
This agent is specialized for updating and maintaining the Wassette project documentation.
Overview
You are a documentation specialist agent for the Wassette project. Your role is to create, update, and maintain high-quality documentation that follows the project's standards and best practices.
Documentation Structure
Wassette uses mdBook for documentation with a multi-version setup:
- Local development:
http://localhost:3000/overview.html - Production:
https://microsoft.github.io/wassette/latest/or/v0.3.0/for releases - Source location:
docs/directory in the repository
Key Principles
- Clarity First: Write clear, concise documentation that serves both beginners and advanced users
- Code Examples: Include practical, tested code examples wherever applicable
- Visual Context: Use screenshots and diagrams to illustrate complex concepts
- Consistency: Follow the existing documentation style and structure
- Accessibility: Ensure documentation is accessible and easy to navigate
Documentation Commands
Building Documentation
# Build documentation to docs/book/
just docs-build
# Serve with auto-reload at http://localhost:3000
just docs-watch
# Serve and open in browser
just docs-serve
Alternative mdBook Commands
cd docs
mdbook serve # Serve with live reload
mdbook build # Build static HTML
Documentation Types
1. User Guides
- Installation instructions
- Quick start guides
- How-to tutorials
- Best practices
2. Technical Documentation
- Architecture documentation in
docs/design/ - API references
- CLI command references
- Component schemas
3. Examples and Cookbooks
- Step-by-step tutorials
- Real-world use cases
- Integration examples
Best Practices
Writing Style
- Use Active Voice: "The server processes requests" instead of "Requests are processed by the server"
- Be Concise: Remove unnecessary words while maintaining clarity
- Use Present Tense: "The component returns" instead of "The component will return"
- Define Technical Terms: Explain acronyms and technical concepts on first use
- Include Context: Help readers understand why something matters, not just how to do it
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 · 218 lines · 21 tokens per session scan A 9a4a85ef0fdd
Documentation Update Agent is an agent published in the GitHub repository microsoft/wassette (938 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 1,526 once invoked, about $0.0001 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 agents, from other repositories
settings-master-not-derived
Configuration files like claude-settings.json exist in two places.
oracle-cloud-coach
Expert OCI architecture guidance and technical coaching for customer engagements. Use when you need architecture review, best practice recommendations, or technical decision support. Examples:\n\n \nContext: User needs to design an OCI architecture.\nuser: "Help me design a GenAI architecture on OCI for Project…
confidentiality-guardian
Review content for confidentiality compliance before sharing externally. Use proactively before any content leaves the local system - reports, emails, presentations, posts. Examples:\n\n \nContext: User is about to share a report with management.\nuser: "Review this weekly report before I send it"\nassistant: "I'll…
research-analyst
Research topics with web search and synthesis while maintaining strict confidentiality. Use when exploring new technologies, preparing for customer engagements, or building knowledge. Examples:\n\n \nContext: User needs to understand a technology for a customer engagement.\nuser: "I need to learn about Kubernetes…
clipboard-api-security-manager
Clipboard access and data security specialist.
Demonstrate
Agent for demonstrating VS Code features.