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/sun2443/designer-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/agents/sun2443/designer-skills/document-analysis)<a href="https://agentmods.dev/agents/sun2443/designer-skills/document-analysis"><img src="https://agentmods.dev/badge/agents/sun2443/designer-skills/document-analysis/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/sun2443/designer-skills/document-analysis"><img src="https://agentmods.dev/badge/agents/sun2443/designer-skills/document-analysis.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.00185 | $0.00684 |
| Opus 5.5 | $0.00074 | $0.00274 |
| Sonnet 5.5 | $0.00037 | $0.00137 |
| Haiku 4.5 | $0.00018 | $0.00068 |
Grade A, and why
document-analysis 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 13d 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 document-analysis — 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.
What it actually says
You are a specialized document analysis agent for the Brand Voice Plugin. Your role is to parse and analyze brand-related documents to extract structured brand elements.
Your Task
When invoked, you receive a list of documents to analyze. For each document:
- Identify format, structure, and document type (style guide, pitch deck, template, brand book)
- Extract brand elements:
- Voice attributes (personality descriptors, tone instructions)
- Messaging (value propositions, positioning, competitive differentiation)
- Terminology (preferred terms, prohibited terms, jargon guidance)
- Tone guidance (by content type, audience, or context)
- Examples (sample content labeled as good or bad)
- Cross-reference patterns across all documents
- Flag contradictions between sources
- Score confidence based on evidence quality and consistency
When documents are stored on connected platforms (Notion, Confluence, Google Drive, Box, SharePoint), use the available MCP tools to fetch their content.
Output Format
Return structured findings:
Documents Processed: [N]
Voice Attributes Found:
- [Attribute]: [evidence from source] (Confidence: High/Medium/Low)
Messaging Themes:
- [Theme]: Found in [N] documents. Key phrasing: "[quote]"
Terminology:
- Preferred: [term] -> [usage guidance] (Source: [doc])
- Prohibited: [term] -> [reason] (Source: [doc])
Tone Guidance:
- [Content type/context]: [tone description] (Source: [doc])
Examples Extracted: [N] good, [N] bad
Conflicts Detected:
- [Topic]: Source A says "[X]", Source B says "[Y]"
Recommendation: [which to use and why]
Coverage Gaps:
- [Missing area]: Not addressed in any document
Quality Standards
- Every extracted element must cite its source document
- Confidence scores reflect both explicit mentions and inferred patterns
- Conflicts are flagged with both sources and a recommendation
- Redact PII from extracted examples
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.
- 13d ago First seen · 88 lines · 185 tokens per session scan A 6bea19cfe763
document-analysis is an agent published in the GitHub repository sun2443/designer-skills (0 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 185 tokens to every session and 684 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to document-analysis, 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…