check-docs

check-docs is a skill for Claude Code from kunalsuri/ai-fication-kit. It costs 57 tokens per session (2,078 once invoked), scanned A, original, Apache-2.0.

A local documentation audit for the kit's README and docs. It compares those documents with the actual commands, skills, plugins, and distributed file tree.

In plain words
What is it for?
Use it to check the kit's own documentation and produce ranked findings. It is a maintainer tool and is not installed into target repositories.
Why use it?
It finds documentation that has fallen out of sync after new features, commands, skills, or files were added.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions AGENTS.md.

Good fit Use it to check the kit's own documentation and produce ranked findings. It is a maintainer tool and is not installed into target repositories.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/kunalsuri/ai-fication-kit/check-docs
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 kunalsuri/ai-fication-kit --skill check-docs
Clone the repo
git clone --depth 1 https://github.com/kunalsuri/ai-fication-kit

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 check-docs

README.md
[![agentmods](https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/check-docs/github.svg)](https://agentmods.dev/skills/kunalsuri/ai-fication-kit/check-docs)
Your own site
<a href="https://agentmods.dev/skills/kunalsuri/ai-fication-kit/check-docs"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/check-docs/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 check-docs

Your own site · 80×15
<a href="https://agentmods.dev/skills/kunalsuri/ai-fication-kit/check-docs"><img src="https://agentmods.dev/badge/skills/kunalsuri/ai-fication-kit/check-docs.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,078 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.02078
Opus 5.5 $0.00023 $0.00831
Sonnet 5.5 $0.00011 $0.00416
Haiku 4.5 $0.00006 $0.00208

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

Security

Grade A, and why

check-docs 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/check-docs/SKILL.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Run the check-docs diagnostic. Read-only. Produce a structured findings report; do NOT edit any file.

Local-only skill. This lives in .claude/skills/check-docs/ with no twin in templates/, so the installer never stamps it into target repos. It audits this kit's own README and docs — it is a maintainer tool, not a distributed workflow. See .claude/LOCAL-ONLY-COMMANDS.md. (Its own file, and any other local-only skill, is therefore expected to be absent from the distributed roster — do not flag that as drift.)

Why this exists

Docs drift silently: a feature adds a command, a skill, or a stamped file, and the prose roster, the What You Get tree, and the counts scattered across the docs quietly fall behind the code. verify/drift//check-drift guard the target-repo knowledge layer (ai/), not the kit's own public docs. This skill closes that gap.

Ground truth — derive these FIRST, from the code, before reading any prose

The distributed reality is defined by templates/, not by .claude/ (which also holds local-only extras like this skill and /implement-spec). Derive, deterministically:

  • Distributed workflows = the sub-directories of templates/claude/skills/ (the Claude surface — custom commands merged into skills). This is the canonical "what users get" roster. Cross-check parity with templates/github/prompts/, templates/agents/workflows/, and templates/cursor/rules/ (a workflow is "universal" only if present in all).
  • Distributed skills = the sub-directories of templates/claude/skills/ and templates/agents/skills/.
  • CLI commands = the members of the authoritative const COMMANDS = new Set([…]) in install.mjs (the CLI's own routing source, also used by test/release-check.mjs) — do not count command === "…" comparisons, which also appear for sub-flows. Mirrored in the docs/CLI-REFERENCE.md "Command index" table.
  • Stamped ai/ tree = the structure under templates/ai/ plus the files install.mjs writes directly (ai/repo-profile.json, ai/install-manifest.json, optionally ai/repo-indepth.json).
  • Local-only skills = present in .claude/skills/ but absent from templates/claude/skills/; the intended list is .claude/LOCAL-ONLY-COMMANDS.md.

Read the full file on GitHub · 141 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 · 141 lines · 57 tokens per session scan A 63628ca9a983

Subscribe to this mod's changes

check-docs is a skill published in the GitHub repository kunalsuri/ai-fication-kit (3 stars, last pushed 6d ago), licensed Apache-2.0. It adds 57 tokens to every session and 2,078 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.