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 skills add bankszach/document-systems --skill compose-document-systemgit clone --depth 1 https://github.com/bankszach/document-systemsWrote 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/bankszach/document-systems/compose-document-system)<a href="https://agentmods.dev/skills/bankszach/document-systems/compose-document-system"><img src="https://agentmods.dev/badge/skills/bankszach/document-systems/compose-document-system/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/skills/bankszach/document-systems/compose-document-system"><img src="https://agentmods.dev/badge/skills/bankszach/document-systems/compose-document-system.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.00078 | $0.00635 |
| Opus 5.5 | $0.00031 | $0.00254 |
| Sonnet 5.5 | $0.00016 | $0.00127 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
compose-document-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 1mo 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compose Document System
Perform the semantic reasoning, then ask the deterministic MCP to construct a proposal-scoped Expression. Render documents as traceable views of that Expression. Do not begin with a universal prose template.
Workflow
- Identify the document's primary job and intended user.
- Call
list_document_profilesand select one primary profile plus no more than one secondary profile. - Read the supplied sources yourself. Mark source review only as
REVIEWED_BY_CALLER; this remains your assertion, not an MCP finding. - Build explicit SourceRefs, semantic elements, and assertions for consequential values or transitions supported by caller-reviewed evidence.
- Prefer
compile_document_packetto compose, validate, gate, and render once. UseSUMMARYfor an efficient review handoff andFULLonly when the caller needs a portable packet to store or transfer. - Use the separate compose, validate, and render tools only when an existing Expression or staged diagnostic workflow requires them.
- Resolve integrity and semantic-assertion failures. Report readiness warnings rather than filling them speculatively.
- Hand off the packet identity, release gate, artifact, and unresolved human decisions. A ready gate still requires a human decision.
Populate only elements supported by the user's request or cited evidence. Keep unknown fields explicit; do not invent authority, acceptance, or proof.
Boundaries
- The Expression state is always
PROPOSED; this skill cannot promote it. - Treat generated requirements, claims, and procedures as proposals.
- Never infer acceptance from validation, a completed checklist, or polished formatting.
- Do not put acceptance, operative status, views, or validation results inside an Expression.
- Do not create multiple independently maintained versions of the same facts.
- Do not force a multi-profile document when one focused profile is enough.
- If the task is a simple low-consequence note, use ordinary writing instead of this system.
- The MCP writes nothing. A FULL packet is portable but remains
NOT_PERSISTED; save it with ordinary repository tools only when the user explicitly requested project writes.
What ships with it
2 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.
- 1mo ago First seen · 65 lines · 78 tokens per session scan A da3e2cd32e4b
compose-document-system is a skill published in the GitHub repository bankszach/document-systems (0 stars, last pushed 2mo ago), licensed MIT. It adds 78 tokens to every session and 635 once invoked, about $0.0003 per session on Opus 5.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
ssotize
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts…
docs-sync-internal
Use when code changes on the current branch need matching internal or developer documentation — "update our internal docs", "the architecture docs are stale after this change", "document what I just changed", "do the dev docs still match the code?" — or as a pre-push check that developer docs track the code. Narrower…
visual-html-renderer
A shared workflow for turning requested content into a final HTML document that can be checked and previewed in a browser. It chooses a document structure, renders it, validates the result, and returns a temporary preview link.
atlas-absorb
A document-reading skill that finds concepts in meeting notes, plans, or pull-request descriptions and connects them to an existing knowledge graph. A knowledge graph stores concepts and their relationships.
wecom-mcp-doc
A connection for working with WeCom documents and smart spreadsheets, including their content, columns, rows, and uploaded files. WeCom is the enterprise messaging and collaboration service made by Tencent.
pdf-image-text-extractor
A tool for reading text from images and PDF files, including scanned documents. OCR means recognizing printed or handwritten characters in an image and turning them into editable text.