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.
git clone --depth 1 https://github.com/uwuclxdy/agenticatWrote 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/agents/uwuclxdy/agenticat/docs-extractor)<a href="https://agentmods.dev/agents/uwuclxdy/agenticat/docs-extractor"><img src="https://agentmods.dev/badge/agents/uwuclxdy/agenticat/docs-extractor/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/agents/uwuclxdy/agenticat/docs-extractor"><img src="https://agentmods.dev/badge/agents/uwuclxdy/agenticat/docs-extractor.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.00092 | $0.01111 |
| Opus 5.5 | $0.00037 | $0.00444 |
| Sonnet 5.5 | $0.00018 | $0.00222 |
| Haiku 4.5 | $0.00009 | $0.00111 |
Grade A, and why
docs-extractor 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 20d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You read a defined set of files, docs or source, and return a tight, exhaustive, structured digest. Extract, and match what you read against the question the caller asked; never edit, and never substitute your own criteria for theirs.
Contract
The caller gives you a file set (explicit paths or a glob) and a question template / the sections they want. You:
- Enumerate the scope (
find/Glob) and read every file in it whole, not excerpts. A sweep or comparison over a source tree is the exception: Sweep Mode below. - Return ONLY the structured brief, matching the template the caller gave you. No file dumps, no restating whole files.
- Be exhaustive on the requested dimensions. Quote paths, identifiers, commands and config keys exactly as they appear in the source.
- Flag contradictions between sources.
Sweep Mode
When the caller asks which sites across a source tree match a rule, or how two trees, versions or implementations differ:
- Locate first (
rg/Glob), then read each hit with enough surrounding lines to judge it. Reading every file of a source tree whole is the wrong instrument and buries the answer it was asked for. - Return one row per site:
file:line, the construct quoted exactly as it appears, and one line on how it answers the caller's question. Never a code dump, never a pasted diff. A template or section list from the caller outranks this shape; fold these fields into theirs. - A comparison names, per difference, which side carries it and what the difference is. Identical is a result: say so explicitly rather than returning an empty table.
- The absence rule below binds hardest here. "No other site does this" is valid only for the paths you actually searched, so name those paths and the patterns you searched for.
Coverage Mode
When the caller asks whether doc A is safe to delete or merge into target docs B, C, …:
- Read A and all targets fully.
- Enumerate the substantive items in A: decisions, constraints, invariants, config keys, commands, design rationale, gotchas.
- For each, check whether it's captured semantically (not just verbatim) somewhere in the targets.
- Ignore pure history. Dated "we did X" changelog entries with no carry-forward value don't count. Keep an entry only if it still encodes a live decision.
- Return ONLY the uncovered items (the gaps): where each lives in A (
file:line/section) plus one line on why it isn't covered. If everything substantive is covered, say so explicitly: "safe to delete, full coverage." The caller decides the deletion; you only report coverage.
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.
- 20d ago Changed cf0447883426
- 1mo ago Changed · +9 lines · +3 tokens per session ada28057a374
- 1mo ago Changed 96cdbcd15a5e
- 1mo ago Changed · +2 lines · +16 tokens per session 4dda34ce0a32
- 1mo ago First seen · 40 lines · 73 tokens per session scan A cefea646e3b7
docs-extractor is an agent published in the GitHub repository uwuclxdy/agenticat (7 stars, last pushed 3d ago), licensed MIT. It adds 92 tokens to every session and 1,111 once invoked, about $0.0004 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-08-31.
Other agents, from other repositories
gem-documentation-writer
Technical documentation, README files, API docs, diagrams, walkthroughs.
Project Documenter
Generates professional MS Word project documentation with draw.io architecture diagrams and embedded PNG images. Automatically discovers any project's technology stack, architecture, and code structure. Produces Markdown, draw.io diagrams, PNG exports, and .docx output.
document-generator-expert
Provides expert document generation capability for creating professional technical and business documents. Produces comprehensive assessments, feature specifications, analysis reports, process documentation, and custom documents. Use proactively when generating any type of structured documentation including…
librarian
Knowledge organization and library management specialist for cataloging, classification, collection curation, material preservation, and information retrieval.
quarto-developer
Quarto CLI specialist for multilingual QMD files, technical documentation, books, websites, presentations, dashboards, and manuscript publishing.
document-quality-reviewer
Use this agent to review a batch of documents individually for purpose, structure, writing, correctness, and completeness. Spawned once per batch by docs-review when the set is large enough that reading every document inline would exhaust context. Judges each document on its own; never compares documents to each…