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/skillmedev/document-studio/document-template-systemnpx skills add SkillMedev/document-studio --skill document-template-systemgit clone --depth 1 https://github.com/SkillMedev/document-studioWhat 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.00124 | $0.01664 |
| Opus 5 | $0.00062 | $0.00832 |
| Sonnet 5 | $0.00025 | $0.00333 |
| Haiku 4.5 | $0.00012 | $0.00166 |
Grade A, and why
Document Template System 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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Template System
A template is not a filled-out document with blanks - it is a decision made once so the team never makes it again. The costly failure is the over-built system: twenty templates nobody uses, each slightly stale, until authors quietly revert to copying last quarter's doc and the formatting drift returns. The best template systems are small, self-explanatory, and maintained by one named person.
Operating procedure
Audit before building, build before standardizing, standardize before naming - each step's output is the next step's input.
Step 1: Audit what the team actually produces
List the top 10 document types by frequency (count real docs from the last quarter; do not poll people on what they think they write). Build templates only for the top 5. Attempting to template everything produces a system nobody uses - every template below the frequency line is pure maintenance debt.
For each of the top 5 candidates, answer three questions before designing anything:
- Who authors this document, and how often?
- Who reads it, and what do they do with it? (A doc that drives a decision is structured differently from a doc that records one.)
- What varies between instances, and what should stay constant? The constant parts become required sections; the varying parts become variables.
If a candidate's answers are all "it depends," it is not one document type - split it or drop it.
Step 2: Build each template with the four-part anatomy
Every template contains exactly these four elements:
- Purpose block - a single paragraph for the author's eyes stating what the template is for, when to use it, and what it is NOT for. This block is deleted before the document is sent.
- Required sections - appear in every instance; label them
REQUIRED. - Optional sections - relevant only sometimes; label them
OPTIONAL - include if [condition]and remove the label when used. The condition must be decidable by the author alone ("include if budget exceeds $10k", not "include if relevant"). - Variables - instance-specific placeholders written as
[VARIABLE NAME IN CAPS]so they are visually distinct and findable with text search. A shipped document containing a raw[VARIABLE]is the system's most visible failure - capitalized bracketed variables make it nearly impossible to miss one.
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.
- yesterday First seen · 116 lines · 124 tokens per session scan A 05142d8c2411
Document Template System is a skill published in the GitHub repository SkillMedev/document-studio (1 stars, last pushed 1mo ago), licensed MIT. It adds 124 tokens to every session and 1,664 once invoked, about $0.0006 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
markdown-documents
Use when creating or editing Markdown documents, notes, reports, briefs, drafts, or other editable writing where Markdown should be the primary artifact format.
writer-documents
Use when creating, opening, or editing LibreOffice Writer ODT documents, or DOCX documents only when Microsoft Word compatibility is explicitly required.
pipefy-reports
Use this skill when the user wants to create, read, update, delete, or export pipe reports or organization reports. Covers the async export workflow (trigger, poll, download). 17 MCP tools.
html-artifact
Create self-contained HTML artifacts (single-file by default, split bundles when oversized) for complex, reviewable, or shareable work outputs. Use for an HTML artifact, browser-viewable report, implementation plan, PR/code-review report, dashboard, or mini deck, or for long Markdown-like outputs needing navigation or…
making-academic-presentations
Create academic presentation slide decks and optionally demo videos from research papers.
erpclaw
AI-native ERP system. Full accounting, invoicing, inventory, purchasing, tax, billing, HR, payroll, advanced accounting (ASC 606/842, intercompany, consolidation), and financial reporting (including P&L / trial balance / spend grouped by department, project, cost center, location, or fund). 496 actions across 14…