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 saajunaid/caddis-plugin --skill documentation-analyzergit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/documentation-analyzer)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/documentation-analyzer"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/documentation-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.
<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/documentation-analyzer"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/documentation-analyzer.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.00023 | $0.00393 |
| Opus 5.5 | $0.00009 | $0.00157 |
| Sonnet 5.5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
documentation-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 19d 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
Documentation Analyzer Skill
When to Use
- Analyzing a codebase for documentation
- Generating README or API docs
- Understanding code structure and patterns
- Creating onboarding documentation
Phase 1: Codebase Discovery
- Map Structure: Identify modules, packages, entry points
- Dependency Analysis: Trace imports and dependencies
- Pattern Recognition: Identify design patterns and architecture
Phase 2: Code Understanding
For each module: Purpose, Dependencies, Exports, Side Effects For functions: Inputs, Outputs, Business logic, Edge cases For classes: Responsibility, Public interfaces, Internal state, Interactions
Phase 3: Documentation Generation
README Structure
# Project Name
## Overview
## Architecture (Mermaid diagram)
## Installation
## Usage (code examples)
## Configuration
## API Reference
## Development (contributing, tests)
API Documentation Format
## `function_name(param1: Type) -> ReturnType`
Brief description.
### Parameters
### Returns
### Raises
### Example
Phase 4: Diagram Generation
graph TB
subgraph Frontend
UI[App UI]
end
subgraph Backend
API[API Layer]
SVC[Services]
end
subgraph Data
DB[(Database)]
end
UI --> API --> SVC --> DB
Checklist
- Project structure mapped
- All modules documented
- README generated
- API docs created
- Architecture diagram included
- Installation/setup instructions clear
- Code examples provided
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.
- 19d ago Changed · -9 tokens per session 925a024a1719
- 1mo ago First seen · 79 lines · 32 tokens per session scan A 4259e999a596
documentation-analyzer is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 393 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
goga-cookbook
Principles for applying DSL specification in cell and CODEMANIFEST design.
goga-review-plan
Verify execution plan completeness and correctness.
goga-define-challenge
Challenge the complete product definition before the PRD is generated.
goga-define-experience
Define the user experience required to achieve the established product goals and solve the identified problem.
goga-define-requirements
Define the product requirements that describe what the product must do to deliver the established user experience and achieve the agreed product goals.
goga-discover
Interview the user relentlessly about a decision until every branch of the design tree is resolved, then record the result as a short ADR.