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/eddiebelaval/squire/document-design-foundationnpx skills add eddiebelaval/squire --skill document-design-foundationgit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/eddiebelaval/squire/document-design-foundation)<a href="https://agentmods.dev/skills/eddiebelaval/squire/document-design-foundation"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/document-design-foundation.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.00019 | $0.04740 |
| Opus 5 | $0.00010 | $0.02370 |
| Sonnet 5 | $0.00004 | $0.00948 |
| Haiku 4.5 | $0.00002 | $0.00474 |
Grade A, and why
Document Design Foundation 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 2d 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 — 571 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Design Foundation
Core Workflows
Workflow 1: Primary Action
- Analyze the input and context
- Validate prerequisites are met
- Execute the core operation
- Verify the output meets expectations
- Report results
This is the shared design system for all document generation in Claude Code. Every document skill (PDF, Report, Word, Presentation, Spreadsheet) references this foundation for consistent, professional output.
The Golden Rule
When the user asks you to create a document, YOU create it. Do not write a program that creates it.
- Generate a beautifully styled HTML file directly using the Write tool
- Save it to the project directory or
~/Development/artifacts/if no project context - Open it in the browser if the user wants to preview
- Convert to PDF via puppeteer only if the user specifically needs a .pdf file
- Convert to .docx only if the user specifically needs a Word file
Operational Workflow
User says "create a report" or "make a PDF" or "generate a document"
|
v
1. Determine document type and content
2. Choose the right template (see Document Types below)
3. Write a single, self-contained HTML file using the design system below
4. Save to appropriate location
5. If user needs .pdf: convert via puppeteer script
6. If user needs .docx: generate via docx library
7. Tell the user where the file is
Design System
Color Palette
Primary: #1a1a2e (deep navy - headings, primary text)
Secondary: #16213e (dark blue - subheadings)
Accent: #0f3460 (medium blue - links, highlights)
Accent Light: #e8f0fe (pale blue - backgrounds, cards)
Success: #0d7c3d (green - positive metrics)
Warning: #b45309 (amber - caution)
Danger: #b91c1c (red - negative metrics, alerts)
Neutral 50: #fafafa (near white - page background)
Neutral 100: #f5f5f5 (light gray - card backgrounds)
Neutral 200: #e5e5e5 (border gray)
Neutral 400: #a3a3a3 (muted text)
Neutral 600: #525252 (body text)
Neutral 800: #262626 (strong text)
Neutral 900: #171717 (headings)
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.
- 2d ago First seen · 571 lines · 19 tokens per session scan A db572335e456
Document Design Foundation is a skill published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 20d ago), licensed MIT. It adds 19 tokens to every session and 4,740 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
design-system
Token architecture and component specs: three-layer tokens (primitive→semantic→component), CSS variables, spacing/typography scales, slide generation. Use for design tokens, systematic design, brand-compliant presentations.
extract-design
Extract the full design language from any website URL. Produces 8 output files including AI-optimized markdown, visual HTML preview, Tailwind config, React theme, shadcn/ui theme, Figma variables, W3C design tokens, and CSS variables. Also runs WCAG accessibility scoring. Use when user says 'extract design', 'get…
design-system-tokens
Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.
documentation-patterns
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
bmad-shard-doc
Splits large markdown documents into smaller, organized files based on level 2 (default) sections. Use if the user says perform shard document.
morphous-catalog
Create or refresh Morphous website design-system/theme bundles from animal, insect, plant, landscape, mineral, weather, or other nature motifs. Use when Codex is asked to generate Morphous motif images, light/dark design-system boards, reusable image prompts, generated web assets, shadcn/tweakcn theme exports, or the…