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 GoogilyBoogily/googilyboogily-claude-power-tools --skill docs-auditgit clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/docs-audit)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/docs-audit"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/docs-audit/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/googilyboogily/googilyboogily-claude-power-tools/docs-audit"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/docs-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00057 | $0.02154 |
| Opus 5 | $0.00028 | $0.01077 |
| Sonnet 5 | $0.00011 | $0.00431 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade A, and why
docs-audit 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Audit
Audit skills, commands, and agents in this repository against the canonical standards defined in docs/. Reads docs/audit-checklists.md as the single source of truth for check criteria, cross-references docs/best-practices.md for evaluation context, and docs/templates.md for valid frontmatter fields and structural patterns.
Produces a markdown report — not an interactive walkthrough. For interactive per-issue resolution, use the artifact-toolkit audit skills instead.
Input
$ARGUMENTS — one of:
- Single path: path to a SKILL.md, agent
.md, or command.mdfile --all: audit every skill, agent, and command across all plugins--type skill|command|agent: audit all artifacts of one type--severity critical|warning|info(optional, combinable): filter report to show only findings at or above this severity (default: show all)
Process
Phase 1: Load Documentation
Read these three files from the project root. These are the authoritative references for all checks:
docs/audit-checklists.md— checklist tables with check IDs and severity levelsdocs/best-practices.md— authoring standards, decision guides, naming conventions, quality criteriadocs/templates.md— canonical frontmatter field references, structural templates, string substitution reference
Parse and retain all three in context. Every check evaluation must trace back to specific criteria from these documents.
Phase 2: Identify Targets
Parse $ARGUMENTS to determine audit mode and targets.
Mode detection:
- If arguments contain
--all: batch mode, all types - If arguments contain
--type skill: batch mode, skills only - If arguments contain
--type command: batch mode, commands only - If arguments contain
--type agent: batch mode, agents only - Otherwise: single-artifact mode using the provided path
Severity filter:
- If
--severity critical: report only 🔴 CRITICAL findings - If
--severity warning: report 🔴 CRITICAL and 🟡 WARNING findings - If
--severity infoor omitted: report all findings
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 · 212 lines · 57 tokens per session scan A 042a91deb7bf
docs-audit is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 2,154 once invoked, about $0.0003 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-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…