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/aj604/toolshed/writing-docsnpx skills add aj604/toolshed --skill writing-docsgit clone --depth 1 https://github.com/aj604/toolshedWhat 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.00190 | $0.01980 |
| Opus 5 | $0.00095 | $0.00990 |
| Sonnet 5 | $0.00038 | $0.00396 |
| Haiku 4.5 | $0.00019 | $0.00198 |
Grade A, and why
writing-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 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Docs
Overview
A doc whose job is to track the repo is a set of claims that must be true of the repo. This is the spine: when any guideline conflicts with verifiability, verifiability wins. A smaller all-true doc beats a complete one with unverifiable parts.
Every assertion unit has one of the document model's four assertion classes:
- Factual — commands, paths, symbols, behavior (output included), structure, values. Must be mechanically checkable against current evidence.
- Normative — instructions and rules. Must name or sit under a current governing source, or record the current owner's judgment.
- Rationale — the "why", tradeoffs, rejected alternatives. Must be marked and coherent with current evidence from a governing decision or implementation source.
- Non-assertive — connective prose or signposting. It carries no truth judgment, and is the only class that does not.
If an assertion cannot discharge its obligation, cut it or mark it explicitly unverifiable; classification never makes a living assertion optional.
Scope: as in the frontmatter above — README/runbook/CLAUDE.md/AGENTS.md/reference (incl. claim-style docs/reference/architecture.md); not a universal theory of documentation — tutorials/narrative-architecture/ADRs stay narrative (growing-docs), never claim-audited.
The rules (these address what agents get wrong)
Strong agents already read package.json and get commands and flags right. They fail on
the subtler things below. Spend your discipline here.
1. Example output is a claim — run it or omit it
Never invent illustrative numbers, sample output, or "looks-right" results. Output you didn't produce is a fabricated claim, even when it's "just an example."
- Run the command, paste the real output.
- If output is environment-dependent (byte sizes, timestamps, hashes), say so instead of pinning a fragile exact value.
- Can't run it? Don't show output.
2. Normative and rationale assertions need current authority
What ships with it
3 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.
- 2d ago First seen · 135 lines · 190 tokens per session scan A 363cba8705e9
writing-docs is a skill published in the GitHub repository aj604/toolshed (2 stars, last pushed 26d ago), licensed MIT. It adds 190 tokens to every session and 1,980 once invoked, about $0.0010 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
tech-design-generation
Generates professional Technical Design Documents following industry-standard engineering practices. This skill activates when the user asks to write a technical design, create an architecture design, draft a design doc, write a technical proposal, do system design, create a technical design document, write an RFC…
test-cases-generation
Generates structured test case sets with multi-dimensional coverage from project code analysis or specification documents. This skill activates when the user asks to write test cases, generate tests, supplement tests, create test coverage, or improve test completeness. It auto-scans the project to extract testable…
idea
Use when exploring a new idea before writing formal specifications. Guides users through iterative discovery, research, and critical analysis to crystallize vague ideas into validated requirement drafts. Includes anti-pseudo-requirement checks, competitive research, demand evidence gathering, and "What if we don't…
test-plan-generation
Generates professional Test Plan and Test Cases documents following IEEE 829 test documentation standards, ISTQB testing methodologies, and Google Testing Blog best practices. This skill activates when the user asks to write a test plan, create test cases, draft a test plan document, create a test cases document…
prd-generation
Generates professional Product Requirements Documents (PRDs) following industry-standard methodologies. This skill activates when the user asks to write PRD, create a product requirements document, draft product requirements, do product planning, do feature planning, write a product spec, or create a product document.…
propagate
Walk an upstream documentation change downstream — when a PRD, SRS, tech-design, or feature spec is edited, find every dependent document, identify which sections are now stale, and interactively update them to keep the entire doc chain consistent. Use after editing any spec-forge document, or run periodically with…