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.
/plugin marketplace add tw93/Wazanpx agentmods add plugins/tw93/waza/waza-checkgit clone --depth 1 https://github.com/tw93/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/plugins/tw93/waza/waza-check)<a href="https://agentmods.dev/plugins/tw93/waza/waza-check"><img src="https://agentmods.dev/badge/plugins/tw93/waza/waza-check.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
waza-check 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 yesterday.
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.
What it actually says
{
"name": "waza-check",
"description": "Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask in any language for code review, issue or PR triage, release gates, publishing follow-through, or project audits. Not for debugging root causes or prose review.",
"version": "3.35.0",
"category": "development",
"source": "./skills/check",
"homepage": "https://github.com/tw93/Waza",
"skills": [
"./"
],
"strict": false
}What ships with it
1 file beside marketplace.json#waza-check 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.
- yesterday First seen · 12 lines scan A e2bba8a49907
waza-check is a plugin published in the GitHub repository tw93/Waza (6,948 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
raven-mcp
Design-intelligence MCP server: audits pages, screens, and diffs for contrast, layout, tap targets, and consistency; carries a design system and a taste profile an agent can consult before writing UI code.
liquid-glass
Apple-style liquid glass: frosted, refracting surfaces for web UI, with the rules that keep them from reading as gray boxes.
motion-design-skills
Motion design fundamentals, engines, and brand elements as installable skills for AI coding agents — timing, typography, color, composition, After Effects, Remotion, logos, and backgrounds.
hyperstack
Disciplined MCP server + skill system. 16 plugins and 121 tools covering designer (6 personalities, 13 page templates, 9 presets), shadcn/ui, design tokens, ui/ux, React Flow v12, Motion v12, Lenis, React 19, Echo, Go, Rust, product-manager, marketing, reflect, and optimizer. 29 skills with adversarial enforcement…
stark-figma-drive
Exporta frames do Figma e faz upload automatico para o Google Drive do cliente.
ui-input-skills
Form systems, search, and filter components for user input and data collection.