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/avinava/document-design-system/analytical-document-designnpx skills add Avinava/document-design-system --skill analytical-document-designgit clone --depth 1 https://github.com/Avinava/document-design-systemWrote 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/avinava/document-design-system/analytical-document-design)<a href="https://agentmods.dev/skills/avinava/document-design-system/analytical-document-design"><img src="https://agentmods.dev/badge/skills/avinava/document-design-system/analytical-document-design.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 | $0.00156 | $0.02113 |
| Opus 5 | $0.00078 | $0.01056 |
| Sonnet 5 | $0.00031 | $0.00423 |
| Haiku 4.5 | $0.00016 | $0.00211 |
Grade A, and why
analytical-document-design 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 3d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytical Document Design
Create documents that help a reader understand what happened, where it is concentrated, why it matters, and what deserves review.
This skill is about the document, not the system that supplies its data. It applies to engineering portfolios, financial reviews, operational audits, inventory analyses, compliance summaries, and product metrics.
The core standard
A strong analytical document has three layers:
- Decision layer — the headline, current state, material risks, notable opportunities.
- Explanation layer — concentration, time, ownership, composition, comparisons.
- Evidence layer — detailed tables, source records, methodology, caveats.
Do not make every fact equally prominent. The document should be understandable in 30 seconds and defensible after 30 minutes. That tension is the whole design problem — a document that only satisfies the first is a poster, and one that only satisfies the second is a data dump.
Workflow
1. Establish the evidence model
Before designing anything, pin down what the numbers actually mean: the unit being measured, the population included and excluded, which values are counts versus estimates, which fields are facts versus inferred classifications, what the dates mean, and whether the dataset is a snapshot or a series.
Write these distinctions into the report. Never depend on the reader guessing them.
Read references/evidence-semantics.md for the full set of distinctions and the traps in each.
2. Reconcile totals
Calculate the control totals before deriving any chart. Included groups must sum to the reported total, excluded populations must appear separately, every percentage needs a named denominator, and rounded labels must not conceal material discrepancies.
Stop and investigate unexplained differences. Styling inconsistent data into apparent authority is the single most damaging thing this skill can do.
3. Derive views that answer distinct questions
Each view should answer something the others do not: current-state ledger, functional concentration, ownership concentration, creation cohorts, recent activity, staleness, version posture, largest units, review candidates.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 194 lines · 156 tokens per session scan A 9c8355666c86
analytical-document-design is a skill published in the GitHub repository Avinava/document-design-system (2 stars, last pushed 8d ago), licensed MIT. It adds 156 tokens to every session and 2,113 once invoked, about $0.0008 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
implementing-feature
Implement a feature from a product/tech spec, URL, GitHub issue, or by auto-selecting the next papercut enhancement. Reads the spec, implements the feature following Streamlit patterns, and creates a merge-ready PR. Use when given a spec folder path, document URL, or issue link to implement, or when asked to implement…
Document Accessibility Wizard
Interactive document accessibility audit wizard. Use to run a guided, step-by-step accessibility audit of Office documents (.docx, .xlsx, .pptx) and PDFs. Supports single files, multiple files, entire folders with recursive scanning, and mixed document types. Orchestrates specialist sub-agents (word-accessibility…
Alt Text & Headings
Alternative text and heading structure specialist for web applications. Use when building or reviewing any page with images, icons, SVGs, videos, figures, charts, or heading hierarchies. Covers meaningful vs decorative images, complex image descriptions, heading levels, document outline, and landmark structure. Can…
document-csv-reporter
Internal helper for exporting document accessibility audit findings to CSV format. Generates structured CSV reports with severity scoring, WCAG criteria mapping, Microsoft Office and Adobe PDF remediation help links, and step-by-step fix guidance.
Excel Accessibility
Excel workbook accessibility specialist. Use when scanning, reviewing, or remediating .xlsx files for accessibility. Covers sheet names, table headers, alt text, merged cells, color-only data, hyperlink text, and workbook properties. Enforces Microsoft Accessibility Checker rules mapped to WCAG 2.1 AA.
cross-document-analyzer
Internal helper for cross-document accessibility pattern detection, severity scoring, template analysis, and remediation tracking. Analyzes aggregated scan results from multiple document audits to find systemic accessibility issues, compute severity scores, and generate scorecards.