Borrowing it
Nothing to install: this file belongs to hlalljie/agent-workflow-presets. 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/hlalljie/agent-workflow-presets/main/.cursor/skills/write-docs/SKILL.mdgit clone --depth 1 https://github.com/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/write-docs)<a href="https://agentmods.dev/skills/hlalljie/agent-workflow-presets/write-docs"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/write-docs/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/hlalljie/agent-workflow-presets/write-docs"><img src="https://agentmods.dev/badge/skills/hlalljie/agent-workflow-presets/write-docs.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.00058 | $0.00936 |
| Opus 5.5 | $0.00023 | $0.00374 |
| Sonnet 5.5 | $0.00012 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
write-docs 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 19d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write docs
Where each kind of information lives is in documentation.mdc, which is always on. This skill is the procedure and the templates.
When to use
- run-task-loop reaches its docs step.
- verify-commit listed "Docs to update".
- archive-plan has architecture information to place.
- The user asks to create, update, or audit docs.
What does this change need?
Map what the change did to the doc that covers it. A change that matches none needs no doc update; say nothing about it.
- Moved, renamed, or deleted files or folders; a new folder —
docs/folder-structure.md - A decision made or reversed —
docs/decisions.md, in the format from workflow.mdc. If there is a plan, record it in the plan'sdecisions.mdfirst. - A flow, a boundary between parts, a contract, or a constraint changed —
docs/architecture.md - A deploy, rollback, restore, or other ops step changed —
docs/runbooks/<task>.md - An env var added, removed, or renamed —
.env.example: the name, one comment line, and a placeholder value, never a real one - What the project is, its status, or how to run it changed —
README.md
Process
- List what the change touched from
git diffor the task: files moved or deleted, public names changed, flows or boundaries changed, env vars, ops steps, decisions. - Map each item with the list above.
- Read the doc, then edit it in place. Replace what changed; do not append a "changes" note. Delete what is no longer true. State current behavior only. Reasons belong in
docs/decisions.md, not inarchitecture.md. - Create a doc only if its kind does not exist yet. Use the template for that kind (below), and add it to
docs/folder-structure.mdin the same change. Do not create empty docs. - Fix stale references. If files, exports, or types moved, were renamed, or were deleted, grep
docs/,tests/manual/,.cursor/rules/, andREADME.mdfor the old paths and names, and fix every hit. - Do not link to plans. If a plan holds information the docs need, move that information into the doc.
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.
- 19d ago First seen · 69 lines · 58 tokens per session scan A 463a92a2664a
write-docs is a skill published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 20d ago), licensed MIT. It adds 58 tokens to every session and 936 once invoked, about $0.0002 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-10-10.
Other skills, from other repositories
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
share-a-library
Use when a managed library is ready to publish to GitHub and hand to teammates as an install command. Run the GitHub publishing steps, then return the exact shareable install command.
build-workspace-docs
Use when regenerating README.md and WORKAREAS.md in a managed library workspace. Always dry-run first to preview changes.
update-installed-skills
Use when syncing or updating previously installed skills to their latest version. Always dry-run updates before applying, and check for breaking changes.