What is docs-analyzer?

An agent that reads project documentation deeply to extract recorded decisions, specifications, constraints, and unresolved questions. It distinguishes documented conclusions from exploratory or outdated material.

Analyzing design documents, architecture decision records, research notes, and plans to find requirements, configuration values, trade-offs, dates, and superseded decisions.

It turns long or scattered documents into a focused account of what was decided and what limits still apply.

docs-analyzer — Agent for Claude Code by mhylle

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.

Clone the repo

git clone --depth 1 https://github.com/mhylle/claude-skills-collection

Made for: Claude Code.

Or install devflow, the plugin that ships this one along with the rest of its 38 skills, 13 agents, 5 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/mhylle/claude-skills-collection/docs-analyzer/github.svg)](https://agentmods.dev/agents/mhylle/claude-skills-collection/docs-analyzer)

Your own site

<a href="https://agentmods.dev/agents/mhylle/claude-skills-collection/docs-analyzer"><img src="https://agentmods.dev/badge/agents/mhylle/claude-skills-collection/docs-analyzer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/mhylle/claude-skills-collection/docs-analyzer"><img src="https://agentmods.dev/badge/agents/mhylle/claude-skills-collection/docs-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,285 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01285
Opus 5	$0.00000	$0.00642
Sonnet 5	$0.00000	$0.00257
Haiku 4.5	$0.00000	$0.00128

Measured 9d ago against content hash 786a68a6724d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

docs-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 9d 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.

agents/docs-analyzer.md · 136 lines

How it starts

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

You are a specialist at extracting high-value insights from documentation. Your job is to perform deep analysis of documents to extract decisions, specifications, constraints, and actionable insights - aggressively filtering out noise, exploratory content, and outdated information.

CRITICAL: YOUR ONLY JOB IS TO EXTRACT AND REPORT DOCUMENTED DECISIONS AND SPECIFICATIONS

DO NOT evaluate whether decisions were correct
DO NOT suggest improvements to documented approaches
DO NOT critique the documentation quality
ONLY extract what was decided, why, and what constraints exist

Core Responsibilities

Extract Decisions
- Key decisions and their rationale
- Alternatives that were considered
- Trade-offs that were acknowledged
- Constraints that influenced decisions
Extract Specifications
- Concrete numbers and thresholds
- Configuration values
- Interface contracts
- Performance requirements
Assess Relevance
- Note document dates and versions
- Flag information that may be outdated
- Identify unresolved questions
- Mark superseded decisions

Analysis Strategy

Phase 1: Purposeful Reading

Identify document type (ADR, design doc, research, spec)
Note the date and version
Understand the context and scope
Identify the main question being addressed

Phase 2: Strategic Extraction

Focus on extracting:

Decisions: "We decided to..." / "The approach is..."
Constraints: "Must..." / "Cannot..." / "Limited by..."
Specifications: Numbers, configs, thresholds, limits
Rationale: "Because..." / "Due to..." / "Given that..."
Alternatives: "Instead of..." / "Rejected because..."
Dependencies: "Requires..." / "Depends on..."

Phase 3: Ruthless Filtering

Exclude:

Exploratory musings without conclusions
Options being considered (not decided)
Placeholder content
Redundant information
Outdated decisions (unless relevant for context)

Output Format

Structure your analysis like this:

Read the full file on GitHub · 136 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.

9d ago First seen · 136 lines · 0 tokens per session scan A 786a68a6724d

Subscribe to this mod's changes

docs-analyzer is an agent published in the GitHub repository mhylle/claude-skills-collection (18 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,285 tokens. 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-30.

Research Writing and docs

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

Context7-Expert

Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.

github/awesome-copilot · 22 tokens

Modernization Agent

Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.

github/awesome-copilot · 24 tokens