microsoft/waza is a Go command-line tool for building and evaluating AI agent skills through test suites, benchmarks, and model comparisons. It is for developers who need to measure and improve how reliably agent skills work. The catalogue entries are Waza's own skills, instructions, agent, and MCP integration.
Borrowing it
Nothing to install: this file belongs to microsoft/waza. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/microsoft/waza/main/.github/skills/azd-publish/SKILL.mdgit clone --depth 1 https://github.com/microsoft/wazaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/microsoft/waza/azd-publish)<a href="https://agentmods.dev/skills/microsoft/waza/azd-publish"><img src="https://agentmods.dev/badge/skills/microsoft/waza/azd-publish.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00094 | $0.01583 |
| Opus 5 | $0.00047 | $0.00792 |
| Sonnet 5 | $0.00019 | $0.00317 |
| Haiku 4.5 | $0.00009 | $0.00158 |
Grade A, and why
azd-publish 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 8d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
azd Extension Publish
Automate version bumps, changelog updates, and PR creation for waza azd extension releases.
When to Use
- Preparing a new release of the waza azd extension
- Bumping the version number (major, minor, or patch)
- Updating the changelog with changes since last release
- Creating a release PR for review
Workflow
Follow these steps in order. Ask the user for input at each decision point.
Step 1: Gather Changes and Update Changelog
Get the current version from version.txt and extension.yaml, then collect commits since the last release:
cat version.txt
# Find the latest azd extension version tags
git tag --list 'azd-ext-microsoft-azd-waza_*' --sort=-v:refname | head -5
# Get commits since last azd extension tag
last_tag=$(git tag --list 'azd-ext-microsoft-azd-waza_*' --sort=-v:refname | head -1)
git log "${last_tag}..HEAD" --oneline --no-decorate
If version.txt and extension.yaml differ, flag it to the user before proceeding.
Summarize the changes grouped by type:
- Added —
feat:commits - Fixed —
fix:commits - Changed —
refactor:,chore:,docs:commits - Removed — any removal-related commits
Present the summary to the user for review.
Then update CHANGELOG.md. The changelog follows Keep a Changelog format.
Perform these updates (using a placeholder version X.Y.Z — the actual version is determined in Step 2):
-
Move Unreleased content: Move any items currently under
## [Unreleased]into a staging area. If[Unreleased]is empty, populate from the git log summary gathered above. -
Populate from commits: Prepare entries grouped under
### Added,### Fixed,### Changedas appropriate based on the commits gathered above.
Hold these changelog entries — the new version section header and comparison links will be finalized after the version is determined in Step 2.
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.
- 8d ago First seen · 169 lines · 94 tokens per session scan A 73ad53696155
azd-publish is a skill published in the GitHub repository microsoft/waza (1,296 stars, last pushed 2d ago), licensed MIT. It adds 94 tokens to every session and 1,583 once invoked, about $0.0005 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
updater_guide
Guidance for checking for and installing Row-Bot updates.