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-docs-reviewgit 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-docs-review)<a href="https://agentmods.dev/skills/mhawthorne/gza/gza-docs-review"><img src="https://agentmods.dev/badge/skills/mhawthorne/gza/gza-docs-review/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-docs-review"><img src="https://agentmods.dev/badge/skills/mhawthorne/gza/gza-docs-review.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.01697 |
| Opus 5 | $0.00010 | $0.00848 |
| Sonnet 5 | $0.00004 | $0.00339 |
| Haiku 4.5 | $0.00002 | $0.00170 |
Grade A, and why
gza-docs-review 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 12d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Review Skill
Evaluate project documentation for accuracy and identify gaps that potential users may encounter.
When to Use
- User asks to review/evaluate documentation
- User asks "are the docs accurate?"
- User asks "what's missing from the docs?"
- Before a release to ensure docs match implementation
Process
Step 1: Discover documentation structure
-
Find all documentation files:
ls docs/ -
Check for README and other root docs:
- README.md
- CONTRIBUTING.md
- CHANGELOG.md
-
Map the documentation structure to understand what's documented.
Step 2: Read the documentation
Read key documentation files:
- README.md (entry point)
- Quick start / getting started guide
- Configuration reference
- API/CLI reference
- Examples/tutorials
Step 3: Verify against implementation
For CLI tools, compare docs against actual --help output:
uv run <tool> --help
uv run <tool> <command> --help
Check for:
- Missing commands - commands in CLI but not in docs
- Missing options - flags/options not documented
- Incorrect syntax - documented syntax doesn't match actual
- Deprecated features - docs mention features that no longer exist
For libraries/APIs:
- Compare documented functions/classes against actual code
- Check if examples still work
- Verify type signatures match
Step 4: Identify information gaps
Look for missing information users commonly need:
Installation & Setup:
- Prerequisites clearly listed?
- Installation steps complete?
- Authentication/credentials setup?
- First-run experience documented?
Core Concepts:
- Key terms defined?
- Architecture/flow explained?
- Data model documented?
Usage:
- Common workflows covered?
- Examples for each major feature?
- Error messages explained?
Troubleshooting:
- Common errors documented?
- FAQ section?
- Debug/verbose mode explained?
Reference:
- All commands/functions documented?
- All options/parameters listed?
- Default values specified?
- Environment variables listed?
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.
- 12d ago First seen · 262 lines · 20 tokens per session scan A 73c4b5d65d17
gza-docs-review is a skill published in the GitHub repository mhawthorne/gza (12 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 1,697 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
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
development
An index of programming guidance for Python, Go, Rust, TypeScript, Java, C++, and shell scripting.
post-build-flow
Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.
tencent-docs
A Tencent Docs assistant for creating, reading, editing, organizing, importing, and exporting online documents, spreadsheets, presentations, diagrams, and forms.
wechat-search
Search WeChat Official Account articles using OpenClaw's web search, Tavily API, and web fetch capabilities with compliance-focused design.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.