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 dhaupin/vant --skill vant-skill-review-docsgit clone --depth 1 https://github.com/dhaupin/vantWrote 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/dhaupin/vant/vant-skill-review-docs)<a href="https://agentmods.dev/skills/dhaupin/vant/vant-skill-review-docs"><img src="https://agentmods.dev/badge/skills/dhaupin/vant/vant-skill-review-docs.svg" alt="Measured on agentmods" 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.00009 | $0.00438 |
| Opus 5 | $0.00005 | $0.00219 |
| Sonnet 5 | $0.00002 | $0.00088 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
review-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 7d 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.
What it actually says
Docs Review
Does this make sense?
Read Like An AI
Agents don't ask questions. They read and act.
Question: Can an AI understand this without human help?
What To Check
1. Clear Purpose
# What's this about?
## This does X
| Check | Issue |
|---|---|
| No header | Can't find topic |
| Vague header | Can't understand |
| No summary | Can't trust |
2. Codeblocks
Every codeblock needs:
// What it does
const x = doThing()
| Check | Issue |
|---|---|
| No explanation | Can't use |
| Wrong language | Can't run |
| Outdated | Won't work |
3. Examples
# Example
```bash
npm install vant
| Check | Issue |
|---|---|
| No examples | Can't try |
| Wrong command | Won't work |
| Partial | Confusing |
4. Structure
## Step 1
## Step 2
## Step 3
| Check | Issue |
|---|---|
| No steps | Can't follow |
| Wrong order | Confusing |
| Missing steps | Stuck |
AI-First Test
Try explaining to another AI:
"Read this doc and do the thing. Tell me what you'd need to know."
If they can't do it, fix the doc.
Output
## Docs Review - [file]
### Purpose
- [CLEAR/VAGUE] Header: [text]
### Codeblocks
- [OK/MISSING] [count] codeblocks explained
### Examples
- [OK/MISSING] Examples work
### Structure
- [OK/ROUGH] Walkthrough complete
Role: Docs Reviewer
Input: Documentation
Output: AI-readable?
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.
- 7d ago First seen · 117 lines · 9 tokens per session scan A 84edf221a83b
review-docs is a skill published in the GitHub repository dhaupin/vant (9 stars, last pushed 8d ago), licensed MIT. It adds 9 tokens to every session and 438 once invoked, about $0.0000 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
commit
Atomic git commit with conventional message. Use when the user says "commit", "save my changes", "commit this", or wants to create a git commit. Stages specific files, writes a conventional commit message with body explaining non-obvious decisions. Never uses git add -A.
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.
skill-packager
Authors Agent Skills v1.0 packages (SKILL.md plus references/scripts), runs packageskill to produce a standards-compliant zip, and uses installskill to add skills from HTTPS, registry, workspace, or an uploaded archive. Use when the user wants to turn documentation, workflows, or code into a portable skill, export a…
workflow-helper
Guidance for creating, managing and executing workflow automations that chain multiple tools and agents together. Use when the user asks about building, listing, running or composing workflows and automated task pipelines.
attendance-signin-sheet
A spreadsheet generator for printable attendance or meeting sign-in sheets. It turns a list of names into rows with columns such as signatures, dates, departments, or employee IDs.
data-analyzer
Guidance for analyzing structured data, generating statistics and producing data-driven insights. Use when the user asks to analyze data, compute statistics, find patterns, or generate analytical reports.