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 clearsmog/claude-skills --skill doc-reviewgit clone --depth 1 https://github.com/clearsmog/claude-skillsWrote 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/clearsmog/claude-skills/doc-review)<a href="https://agentmods.dev/skills/clearsmog/claude-skills/doc-review"><img src="https://agentmods.dev/badge/skills/clearsmog/claude-skills/doc-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/clearsmog/claude-skills/doc-review"><img src="https://agentmods.dev/badge/skills/clearsmog/claude-skills/doc-review.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.00045 | $0.00747 |
| Opus 5.5 | $0.00018 | $0.00299 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00075 |
Grade A, and why
doc-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 15d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Universal Review
Auto-detect file format and launch the right review agents in parallel. Read-only — no fixes applied.
Format Detection
Determine file type from extension:
.tex→ Beamer LaTeX slides.qmd→ Quarto RevealJS slides.typ→ Typst document (slides, docs, guides, CVs).py→ Python script.md→ Markdown
For .typ files, also detect document type from content:
- Contains
#import "@preview/polylux"or#import "@preview/touying"→ Typst slides - Contains
#import "@local/qk"→ Uses qk component library - Contains
#set page(width: 16cm, height: 9cm)or similar → Presentation - Otherwise → Typst document (guide, essay, CV, etc.)
Routing Table
| Extension | Agents (parallel) | Condition |
|---|---|---|
.tex |
proofreader + document-auditor + pedagogy-reviewer | Always |
.tex |
+ diagram-reviewer | If TikZ found (\begin{tikzpicture}) |
.qmd |
proofreader + document-auditor + writing-style-critic | Always |
.qmd |
+ quality-critic | If .tex sibling exists |
.typ |
typst-reviewer + proofreader + writing-style-critic | Always |
.typ |
+ pedagogy-reviewer | If slide format detected |
.py |
general-purpose subagent with a Python code-review brief | Always |
.md |
proofreader + writing-style-critic | Always |
Steps
- Parse
$ARGUMENTS— resolve file path - Detect format from extension
- For
.typfiles, read file to detect document subtype - Launch agents in parallel per routing table
- Save each agent's returned report to
quality_reports/at the path named in that agent's Output section (read-only agents return their report as text instead of writing it), then collect them - Synthesize a consolidated summary table
Output
# Review Summary: [Filename]
| Dimension | Agent | Critical | Major | Minor | Verdict |
|-----------|-------|----------|-------|-------|---------|
| [varies] | [agent name] | N | N | N | [status] |
## Overall: [EXCELLENT / GOOD / NEEDS WORK / POOR]
## Critical Issues (if any)
[List top issues requiring immediate attention]
## Reports Generated
- quality_reports/[file]_report.md
- quality_reports/[file]_typst_review.md
- ...
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.
- 15d ago First seen · 80 lines · 45 tokens per session scan A 14eb4cf671b1
doc-review is a skill published in the GitHub repository clearsmog/claude-skills (2 stars, last pushed 15d ago), licensed MIT. It adds 45 tokens to every session and 747 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-10-02.
Other skills, from other repositories
godot-code-review
Use when reviewing GDScript or C# Godot code — checklist of best practices, common anti-patterns, and Godot-specific pitfalls. Triggers on "review this script", "check my code", "any issues with this", "what's wrong with this code", including a short pasted snippet.
domain
Domain-specific: SAP Commerce, OpenSearch detection, WordPress validation, enterprise search.
roast
Constructive critique via 5 HackerNews personas with claim validation.
review
Code review: systematic single-file, parallel multi-reviewer, full-repo audit, PR diff review.
improve-code-quality
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy…
refactoring-patterns
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when…