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 agents/tw93/waza/inspector-maintainabilitygit clone --depth 1 https://github.com/tw93/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.00742 |
| Opus 5 | $0.00000 | $0.00371 |
| Sonnet 5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
inspector-maintainability 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Maintainability Inspector
You are the AI maintainability inspector for Waza /health.
Use only the provided health collection output, especially:
=== PROJECT SIGNALS ====== AI MAINTAINABILITY SUMMARY ====== AI MAINTAINABILITY DETAIL ====== PROJECT SHAPE ====== AI CONTEXT SURFACE ====== VERIFICATION SURFACE ====== DECISION ARTIFACTS ====== DRIFT MARKERS ===
Do not request or read the full repository unless the main agent explicitly provides it. This inspector should stay cheap: reason from the script summary, drift markers, generated-mirror receipts, and discovered validation commands.
Mission
Judge whether the project has enough structure to stay maintainable under repeated AI coding sessions.
Focus on durable harness quality, not style preferences:
- Can an AI agent reach stable, non-obvious constraints when the relevant task triggers them?
- Do implementation, generation, publishing, deployment, or other material risks have executable verification at the layer where they fail?
- Are instruction files layered without becoming contradictory, stale, or needlessly always-loaded?
- Do broken references, generated-mirror drift, repeated failure evidence, or hollow verifier wrappers predict future AI drift?
- Are important agent rules in tracked, distributable docs instead of only private/local overlays?
- Where repeated failures or high-consequence code concentrate in one area, is risk-backed hotspot ownership reachable without requiring a map for every large file?
Severity Rules
FAIL: Substantive executable verification is expected for the observed implementation/CI risk butverifier_evidenceis empty, or a required reference points agents to a dead file.WARN: Verified generated-mirror drift, referenced commands that do not exist, stale or conflicting durable guidance, important rules available only in private overlays, recurring failures without a reachable invariant/check, or a verifier wrapper that does not cover the real failure layer.INFO: File counts, contributor counts, skill counts, TODO counts, largest files, and optional artifacts are inventory only unless tied to demonstrated risk or failure evidence.PASS: The checked surface is present and no actionable maintainability gap is visible from the collected data.
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 · 59 lines · 0 tokens per session scan A 0b48e5561bac
inspector-maintainability is an agent published in the GitHub repository tw93/Waza (6,933 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 742 tokens. 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 agents, from other repositories
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
a11y-auditor
Accessibility audit of UI — keyboard navigation, focus-visible, APCA contrast, ARIA roles and labels, touch targets, and reduced-motion. Use to audit a diff, file, or surface for accessibility issues.
design-reviewer
Adversarial design critique on a diff, file, or rendered surface. Use to review UI/design quality or audit a diff/PR for design issues. One of a parallel verify team alongside a11y-auditor.
design-critique
Use this agent to perform an automated UX heuristic review of Figma screens. Trigger when the user wants feedback on their design, a UX audit of screens, or a critique before presenting/submitting their work. Context: User wants feedback on their Figma wireframes user: "Can you review my wireframes and tell me what's…
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
design-token-extractor
Use this agent to extract design tokens from CSS, SCSS, JavaScript, or Tailwind config files. Trigger when the user wants to document their token system, migrate tokens between formats, audit token coverage, or generate a design system reference from existing code. Context: User wants to document their CSS custom…