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/gyanranjan/polyagent-skills/document-analyzernpx skills add gyanranjan/polyagent-skills --skill document-analyzergit clone --depth 1 https://github.com/gyanranjan/polyagent-skillsWrote 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/gyanranjan/polyagent-skills/document-analyzer)<a href="https://agentmods.dev/skills/gyanranjan/polyagent-skills/document-analyzer"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/document-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.1 | $0.00073 | $0.00990 |
| Opus 5 | $0.00036 | $0.00495 |
| Sonnet 5 | $0.00015 | $0.00198 |
| Haiku 4.5 | $0.00007 | $0.00099 |
Grade A, and why
document-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 5d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Analyzer
Purpose
Rapidly understand and extract structured insights from any document — technical docs, reports, contracts, research papers, policies, or any text-heavy material. Produces a clear analysis that helps the user grasp the document's key content without reading it end-to-end.
When to Use
- User uploads or shares a document and asks to understand it
- User needs key points extracted from a long document
- User asks "what does this say" about a document
- User needs to compare multiple documents
- User wants to quickly get up to speed on unfamiliar material
When NOT to Use
- User wants to write or create a new document (that's authoring)
- The "document" is actually an email thread (use
mail-summarizer) - User wants requirements extracted (use
requirement-study)
Inputs
Required:
- The document(s) to analyze
Optional:
- Specific questions — what the user wants to know
- Context — why they're reading this, what they'll use it for
- Comparison targets — if comparing multiple documents
Process
Step 1: Initial Assessment
Quickly determine:
- Document type (technical spec, contract, report, research paper, policy, etc.)
- Length and structure
- Intended audience of the document
- Date and currency of the information
Step 2: Structural Analysis
Map the document's structure:
- Major sections and their purpose
- Key arguments or themes
- Data, figures, or tables present
- References and dependencies
Step 3: Content Extraction
Extract based on document type:
For Technical Documents:
- Core technology/approach described
- Key decisions and their rationale
- Dependencies and requirements
- Limitations and known issues
For Reports/Research:
- Main findings and conclusions
- Methodology (brief)
- Data highlights and key metrics
- Recommendations
For Contracts/Policies:
- Key obligations and rights
- Important dates and deadlines
- Conditions and exceptions
- Risks and liabilities
For General Documents:
- Main message/thesis
- Supporting arguments
- Action items or implications
- Context and background
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.
- 5d ago First seen · 148 lines · 73 tokens per session scan A bab80b387412
document-analyzer is a skill published in the GitHub repository gyanranjan/polyagent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 73 tokens to every session and 990 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
pdf-processing
Extract text from PDFs, fill forms, and merge documents.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…
file-to-markdown-docker
Run Apache Tika as a Docker container when you need guaranteed OCR (scanned PDFs, images) or geospatial raster support with zero local install — apache/tika: -full bundles Tesseract, GDAL, ImageMagick, and fonts. Also covers the minimal image, port/volume/memory conventions, the path-identity mount gotcha, and how to…
publishing
Publishing Stencila documents - rendering to HTML/PDF/DOCX with themes, building and pushing workspace sites, publishing to Ghost or Zenodo, and signing outputs with content credentials. Use when the user wants to publish, deploy a site, apply a theme, produce final outputs, or push to Ghost, Zenodo or Stencila Cloud.
conversion
Converting documents between formats with stencila convert - lossless vs lossy targets, quantifying conversion losses, decoding options, and ingesting documents by DOI, arXiv, or PubMed Central identifier. Use when converting to or from DOCX, PDF, LaTeX, JATS, IPYNB, MyST, Quarto or other formats, or importing…