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 skills/microsoft/waza/countnpx skills add microsoft/waza --skill countgit 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.00000 | $0.00424 |
| Opus 5 | $0.00000 | $0.00212 |
| Sonnet 5 | $0.00000 | $0.00085 |
| Haiku 4.5 | $0.00000 | $0.00042 |
Grade A, and why
count 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.
This is a copy
100% identical to all-pass — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
---
name: test-skill
description: |
**TEST SKILL** - A sample skill for testing waza token counting.
USE FOR: testing token count command, verifying markdown scanning.
DO NOT USE FOR: actual agent operations.
---
# Test Skill
A demonstration skill used for testing the `waza tokens` command suite.
## Skill Activation Triggers
**Use this skill when:**
- Running unit tests for token counting
- Verifying file scanning behavior
- Testing output formats (table, JSON)
## Instructions
1. **Scan files** - Find all markdown files in the skill directory
2. **Count tokens** - Estimate token usage for each file
3. **Report results** - Output in requested format
## Output Format
Structure results as:
| File | Tokens | Characters | Lines |
|------|--------|------------|-------|
| SKILL.md | 150 | 600 | 40 |
| README.md | 50 | 200 | 15 |
## Examples
### Example 1: Count All Files
```bash
waza tokens count
Example 1b: Count a Specific Directory
waza tokens count ~/my-skill
waza tokens count references
Output:
File Tokens Chars Lines
------------------------------------
README.md 50 200 15
SKILL.md 150 600 40
Example 2: JSON Format
waza tokens count --format json
Output:
{
"totalTokens": 200,
"totalFiles": 2,
"files": {
"README.md": {"tokens": 50},
"SKILL.md": {"tokens": 150}
}
}
Behavior Guidelines
- Only count markdown files (.md, .mdx)
- Skip binary and non-text files
- Respect .gitignore patterns
- Use streaming for large file sets
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 84 lines · 0 tokens per session scan A 99c4fcdddedf
count is a skill published in the GitHub repository microsoft/waza (1,288 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 424 tokens. A static security scan graded it A with 0 findings. It is 100% identical to all-pass, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.