Borrowing it
Nothing to install: this file belongs to loerei/chronicle-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loerei/chronicle-mcp/main/.agents/skills/write-skill-subdocs/SKILL.mdgit clone --depth 1 https://github.com/loerei/chronicle-mcpWrote 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/loerei/chronicle-mcp/write-skill-subdocs)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/write-skill-subdocs"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/write-skill-subdocs.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.00025 | $0.00796 |
| Opus 5 | $0.00013 | $0.00398 |
| Sonnet 5 | $0.00005 | $0.00159 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
write-skill-subdocs 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write Skill Subdocs
Extract heavy reference material (lookup tables, schemas, templates) from SKILL.md into auxiliary sub-documents (REFERENCE.md or <DOMAIN>.md) via progressive disclosure.
Workflow
flowchart TD
Start["Target SKILL.md"] --> Audit["1. Inventory & Log brain/RATIONALE.md"]
Audit --> Evaluate{"Evaluate Routing Gates"}
Evaluate -->|"No signals & < 150 lines"| Gate0["Gate 0: No Extraction (Exit)"]
Evaluate -->|"Global shared references"| Gate1["Gate 1: Single REFERENCE.md"]
Evaluate -->|"Branch-specific domains"| Gate2["Gate 2: Multiple DOMAIN.md"]
Gate1 --> Plan["Draft Subdocs & Refactor Plan"]
Gate2 --> Plan
Plan --> UserGate{"User Approval Gate"}
UserGate -->|"Revisions"| Plan
UserGate -->|"Approved"| Apply["Apply Edits & agents distribute"]
Directives
- Optimization Invariant: MUST minimize $\sum(\text{reference bytes loaded per execution path})$ per HEURISTICS.md.
- 1-Level Depth Limit: Extracted sub-documents MUST be 1-level deep relative to
SKILL.md; NEVER link nested sub-documents from within a subdoc. - No Over-Specification: When linking extracted subdocs from
SKILL.md, MUST use concise topic anchors (e.g.,- Domain rules: see [DOMAIN.md](DOMAIN.md)) without cataloging internal contents. - Approval Gate: NEVER edit target
SKILL.mdor write subdocs before presentingRATIONALE.mdand obtaining explicit user approval.
Routing Gates
| Gate | Condition | Action |
|---|---|---|
| Gate 0 (No Extraction) | No primary signals in HEURISTICS.md AND linear prose < ~150 lines | Log rationale in RATIONALE.md and exit without modifying files. |
| Gate 1 (Single Subdoc) | Primary signals present, but references are globally needed across all paths | Extract to single REFERENCE.md. |
| Gate 2 (Domain Subdocs) | Primary signals present and isolated to independent execution branches | Extract to multiple <DOMAIN>.md files (Overlapping Subdocs Principle). |
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 · 67 lines · 25 tokens per session scan A 04ba07bf3b9c
write-skill-subdocs is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 796 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…