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 skills add mhawthorne/gza --skill gza-test-and-fixgit clone --depth 1 https://github.com/mhawthorne/gzaWrote 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/mhawthorne/gza/gza-test-and-fix)<a href="https://agentmods.dev/skills/mhawthorne/gza/gza-test-and-fix"><img src="https://agentmods.dev/badge/skills/mhawthorne/gza/gza-test-and-fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mhawthorne/gza/gza-test-and-fix"><img src="https://agentmods.dev/badge/skills/mhawthorne/gza/gza-test-and-fix.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 54 Skill allows unbounded resource consumption (API calls, storage, compute). Without rate limits or quotas, a compromised or misbehaving agent can cause denial-of-service or cost overruns.Fix: Set explicit rate limits, timeouts, and resource quotas for API calls, file operations, and compute. Implement circuit breakers for runaway loops.
- low Excessive Agency · line 53 Skill's behavior or capabilities extend beyond its stated purpose. Scope creep allows an agent to perform actions unrelated to its documented functionality, increasing the attack surface.Fix: Limit the skill's scope to its documented purpose. Remove instructions that enable the agent to perform actions outside its stated functionality.
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.00025 | $0.00711 |
| Opus 5 | $0.00013 | $0.00356 |
| Sonnet 5 | $0.00005 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
gza-test-and-fix 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 11d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test and Fix
Run the project's verify_command (from gza.yaml), fix any errors, and commit all fixes.
Process
Step 1: Get verify_command
Read verify_command directly from gza.yaml and note inner_verify_command if present. If uv run gza config is available in this environment, you may use it as an optional confirmation or to inspect merged config, but do not treat gza config failure as an error when gza.yaml was readable. If verify_command is empty or not set in gza.yaml, stop and tell the user to set verify_command in gza.yaml.
Step 2: Run verify_command and fix errors (max 3 iterations)
Repeat up to 3 times:
- Run the verify_command and capture the output.
- If there are no errors or failures, stop.
- Fix errors by reading the affected files and editing them. Fix anything that is broken, regardless of whether it was changed on the current branch — the goal is a green verify.
- After fixing, increment the iteration counter and continue to the next iteration.
Important: Run the full verify_command each iteration. Do NOT filter or skip test files. All errors and failures are relevant. Fix the root cause in the source, not the test.
If errors remain after 3 iterations, report them to the user.
Step 3: Commit all fixes
If any files were modified during Step 2:
-
Run
git statusandgit diff --name-onlyto see what changed. -
Stage the modified files with
git add <file>for each file (do not usegit add -A). -
If there are uncommitted changes already on the current branch, include your fixes in a single new commit on top (do NOT amend someone else's work). If the working tree was clean before you started (no prior uncommitted work), your fixes form a fresh new commit.
-
Commit with a descriptive message summarising what was fixed, e.g.:
Fix mypy and pytest errors - Fixed type errors in src/foo/bar.py - Fixed failing test in tests/test_bar.py
If no files were modified, report that no fixes were needed.
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.
- 11d ago First seen · 58 lines · 25 tokens per session scan A fcd1f0f85a8b
gza-test-and-fix is a skill published in the GitHub repository mhawthorne/gza (12 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 711 once invoked, about $0.0001 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
trulens-evaluation-workflow
Systematically evaluate your LLM application with TruLens.
agent-builder
Load before calling build-agent for a new or existing n8n Agent. Governs prerequisite creation, faithful handoff of the user's request, agent targeting across turns, builder questions, testing, and publishing. Use directly for routine follow-ups when the conversation already targets an Agent; rerun intent-recognition…
config-evals
Builds and maintains configuration-based evaluations on a workflow with the eval-config tool. Use when the user asks to set up, add, view, change, or remove an evaluation, score, grade, or judge a workflow's output, or measure answer quality against a test dataset. This is the only eval form Instance AI handles — it…
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
ccg-workflow
How to run a non-trivial change end to end with the CCG role tools (ccganalyze / ccgdesign / ccgbuild / ccgdebug / ccgoptimize / ccgreview / ccgtest) and the verify- quality gates. Use when a task is a whole feature, a refactor, a bug whose cause is not yet known, or any change large enough that one straight-through…
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.