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 agentmods add skills/matteocervelli/llms/doc-analyzernpx skills add matteocervelli/llms --skill doc-analyzergit clone --depth 1 https://github.com/matteocervelli/llmsWrote 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/matteocervelli/llms/doc-analyzer)<a href="https://agentmods.dev/skills/matteocervelli/llms/doc-analyzer"><img src="https://agentmods.dev/badge/skills/matteocervelli/llms/doc-analyzer.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 | $0.00023 | $0.04027 |
| Opus 5 | $0.00012 | $0.02014 |
| Sonnet 5 | $0.00005 | $0.00805 |
| Haiku 4.5 | $0.00002 | $0.00403 |
Grade A, and why
doc-analyzer 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 2d 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 — 641 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
The doc-analyzer skill provides comprehensive capabilities for analyzing fetched library and framework documentation to extract actionable implementation guidance. This skill helps the Documentation Researcher agent identify relevant code patterns, best practices, common pitfalls, and integration strategies that enable high-quality feature implementations.
This skill emphasizes:
- Pattern Recognition: Identify reusable code patterns and architectural approaches
- Best Practice Extraction: Discover recommended practices from authoritative sources
- Example Compilation: Collect and categorize working code examples
- Pitfall Identification: Recognize common mistakes and antipatterns
- Integration Guidance: Extract patterns for combining libraries and frameworks
The doc-analyzer skill ensures that documentation research provides practical, actionable guidance rather than raw documentation dumps.
When to Use
This skill auto-activates when the agent describes:
- "Analyze documentation for..."
- "Extract patterns from..."
- "Identify best practices..."
- "Find examples of..."
- "Discover common pitfalls..."
- "Extract API usage patterns..."
- "Analyze integration approaches..."
- "Identify security considerations..."
Provided Capabilities
1. Code Pattern Extraction
What it provides:
- Initialization and setup patterns
- Common usage patterns
- Integration patterns between libraries
- Configuration patterns
- Testing patterns
Pattern Categories:
Initialization Patterns:
def extract_initialization_patterns(docs: dict) -> list:
"""
Extract initialization and setup patterns from documentation.
"""
keywords = [
"setup", "initialize", "config", "configuration",
"getting started", "first steps", "__init__", "setup.py"
]
patterns = []
for section in docs["sections"]:
if contains_keywords(section, keywords):
patterns.append({
"type": "initialization",
"title": section["title"],
"code": extract_code_blocks(section),
"description": section["description"],
"prerequisites": extract_prerequisites(section)
})
return patterns
# Example extracted pattern
{
"type": "initialization",
"title": "FastAPI Application Setup",
"code": """
from fastapi import FastAPI
app = FastAPI(
title="My API",
description="API description",
version="1.0.0"
)
""",
"description": "Basic FastAPI application initialization with metadata",
"prerequisites": ["fastapi installed", "Python 3.7+"]
}
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 641 lines · 23 tokens per session scan A 03e3fb62a22e
doc-analyzer is a skill published in the GitHub repository matteocervelli/llms (25 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 4,027 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…