docs-audit

docs-audit is a skill for Claude Code from GoogilyBoogily/googilyboogily-claude-power-tools. It costs 57 tokens per session (2,154 once invoked), scanned A, original, MIT.

A tool that checks skills, commands, and agents against the standards in a project's documentation.

In plain words
What is it for?
Use it to audit one artifact or all artifacts, choose a type such as skill, command, or agent, and filter the resulting Markdown report by severity.
Why use it?
It turns scattered authoring rules into a consistent audit and reports issues by severity, making gaps easier to find before release.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

Good fit Use it to audit one artifact or all artifacts, choose a type such as skill, command, or agent, and filter the resulting Markdown report by severity.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/googilyboogily/googilyboogily-claude-power-tools/docs-audit
Install

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.

Any agent
npx skills add GoogilyBoogily/googilyboogily-claude-power-tools --skill docs-audit
Clone the repo
git clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-tools

Made for: Claude Code.

Wrote 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.

agentmods badge for docs-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/docs-audit/github.svg)](https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/docs-audit)
Your own site
<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.

agentmods 80×15 button for docs-audit

Your own site · 80×15
<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>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,154 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.02154
Opus 5.5 $0.00023 $0.00862
Sonnet 5.5 $0.00011 $0.00431
Haiku 4.5 $0.00006 $0.00215

Measured 1mo ago against content hash 042a91deb7bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.claude/skills/docs-audit/SKILL.md · 212 lines

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 .md file
  • --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:

  1. docs/audit-checklists.md — checklist tables with check IDs and severity levels
  2. docs/best-practices.md — authoring standards, decision guides, naming conventions, quality criteria
  3. docs/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 info or omitted: report all findings

Read the full file on GitHub · 212 lines

Changes

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.

  1. 1mo ago First seen · 212 lines · 57 tokens per session scan A 042a91deb7bf

Subscribe to this mod's changes

docs-audit is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 5mo ago), licensed MIT. It adds 57 tokens to every session and 2,154 once invoked, about $0.0002 per session on Opus 5.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.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

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"…

umputun/revdiff · 84 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens