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/waza/agents-mdgit clone --depth 1 https://github.com/microsoft/wazaWhat 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.02359 | $0.02359 |
| Opus 5 | $0.01179 | $0.01179 |
| Sonnet 5 | $0.00472 | $0.00472 |
| Haiku 4.5 | $0.00236 | $0.00236 |
Grade A, and why
waza 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 — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions for waza Repository
Overview
This repository contains waza, a CLI tool for evaluating Agent Skills. The primary implementation is Go in the repository root. The Python implementation (waza/) is legacy and no longer actively developed.
When making changes, follow these guidelines to maintain consistency and quality.
Project Tracking
Keep issues and tracking up to date:
- Tracking Issue: #66 - Waza Platform Roadmap
- PRD: docs/PRD.md
- When completing work, update the relevant GitHub issue
- Reference issue numbers in commit messages (e.g.,
feat: Add tokens command #47)
Code Structure (Go - Primary)
cmd/waza/ # CLI entrypoint
└── main.go # Command parsing and execution
internal/
├── config/ # Configuration with functional options
├── execution/ # AgentEngine interface and implementations
│ ├── engine.go # Core engine interface
│ ├── mock.go # Mock engine for testing
│ └── copilot.go # Copilot SDK integration
├── models/ # Data structures
│ ├── spec.go # EvalSpec (eval configuration)
│ ├── testcase.go # TestCase (task definition)
│ └── outcome.go # EvaluationOutcome (results)
├── orchestration/ # EvalRunner for coordinating execution
│ └── runner.go # Eval orchestration
└── scoring/ # Validator interface and implementations
├── validator.go # Validator registry pattern
└── code_validators.go # Code and text validators
go.mod
go.sum
Makefile # Build and test commands
.golangci.yml
Go Naming Conventions
The Go implementation uses idiomatic Go naming:
| Concept | Go Name | Python Equivalent |
|---|---|---|
| Eval configuration | EvalSpec |
EvalSpec |
| Executor | AgentEngine |
BaseExecutor |
| Grader | Validator |
Grader |
| Task | TestCase |
Task |
| Result | EvaluationOutcome |
EvalResult |
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 · 278 lines · 2,359 tokens per session scan A cfdb6d98dd4b
waza AGENTS.md is an instructions file published in the GitHub repository microsoft/waza (1,288 stars, last pushed 3d ago), licensed MIT. It adds 2,359 tokens to every session, about $0.0118 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
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.