some-exceed

A sample skill named test-skill for checking how a skill describes its triggers, instructions, output format, and examples. It is part of a test for the Waza token-counting command.

In plain words
What is it for?
Use it to test scanning Markdown files, estimating token usage, checking output formats, and verifying the Waza token-count command. It is explicitly not intended for actual agent operations.
Why use it?
It provides a fixed example for testing file scanning and token-count reporting without representing a real production operation.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/microsoft/waza/some-exceed
Any agent
npx skills add microsoft/waza --skill some-exceed
Clone the repo
git clone --depth 1 https://github.com/microsoft/waza

Made for: Claude Code, Codex.

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 424 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

What 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.

ModelPer sessionOnce 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

Measured 3d ago against content hash 99c4fcdddedf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

some-exceed 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 3d 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.

Origin

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.

cmd/waza/tokens/testdata/check/some-exceed/SKILL.md · 84 lines

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
Files

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.

Changes

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.

  1. 3d ago First seen · 84 lines · 0 tokens per session scan A 99c4fcdddedf

Subscribe to this mod's changes

some-exceed is a skill published in the GitHub repository microsoft/waza (1,288 stars, last pushed 4d 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

obra/superpowers · 37 tokens

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.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens