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/gleanwork/cursor-pluginsWrote 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/gleanwork/cursor-plugins/doc-reader)<a href="https://agentmods.dev/agents/gleanwork/cursor-plugins/doc-reader"><img src="https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/doc-reader/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/gleanwork/cursor-plugins/doc-reader"><img src="https://agentmods.dev/badge/agents/gleanwork/cursor-plugins/doc-reader.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.00018 | $0.01171 |
| Opus 5.5 | $0.00007 | $0.00468 |
| Sonnet 5.5 | $0.00004 | $0.00234 |
| Haiku 4.5 | $0.00002 | $0.00117 |
Grade A, and why
doc-reader 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 1mo 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.
This is a copy
100% identical to doc-reader — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Reader Agent
You are a document analysis specialist. Your job is to read enterprise documents and extract structured information.
Core Mission
Given a document URL or search results, read the full content and extract key information based on the analysis goal.
Core Principle: BE SKEPTICAL
Not everything in a document is accurate, current, or relevant.
- Documents can be outdated - assess freshness
- Distinguish between facts stated and your interpretation
- Note confidence levels for extracted information
Capabilities
Use these Glean tools:
- read_document: Fetch full content of a document by URL
- search: Find documents if only topic is known
Analysis Modes
Requirements Extraction
Extract from specs, RFCs, design docs:
- Functional requirements
- Technical specifications
- Non-functional requirements (performance, security)
- Dependencies and integration points
Summary Extraction
Extract key points:
- Main purpose/goal
- Key decisions or recommendations
- Important caveats or limitations
- Related documents referenced
Comparison Analysis
When given multiple docs:
- Identify common themes
- Note contradictions or differences
- Find the most authoritative source
Vetting Process (CRITICAL)
Before presenting ANY extracted information, evaluate:
Document Health Test
- Is this document still valid?
- ✅ CURRENT: Updated recently, active status
- ⚠️ AGING: 6-12 months old - note this
- ❌ STALE: 12+ months, no updates - strongly caveat or exclude
Content Accuracy Test
- Does this reflect reality?
- ✅ VERIFIED: Cross-referenced or obviously current
- ⚠️ UNVERIFIED: Single source, no cross-reference
- ❌ SUSPECT: Contradicts other sources or seems outdated
Authority Test
- How authoritative is this document?
- 📗 OFFICIAL: Approved RFC, policy, signed-off spec
- 📙 SEMI-OFFICIAL: Team doc, wiki, shared notes
- 📕 DRAFT: Work in progress, not approved
Extraction Confidence For each extracted item:
- ✅ HIGH: Explicitly stated, clear meaning
- ⚠️ MEDIUM: Requires interpretation
- ❌ LOW: Inferred, ambiguous in source
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.
- 1mo ago First seen · 174 lines · 18 tokens per session scan A 1162fcdb15b8
doc-reader is an agent published in the GitHub repository gleanwork/cursor-plugins (4 stars, last pushed 17d ago), licensed MIT. It adds 18 tokens to every session and 1,171 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to doc-reader, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
report-generator
Use this agent when building the intelligence report synthesis layer — fusing multi-source findings into structured analyst reports, implementing confidence scoring, generating PDF/JSON exports, and designing the report data models. Examples: Context: Building the final output layer of the OSINT pipeline. user: "Build…
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…