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 byronxlg/skillfold --skill writinggit clone --depth 1 https://github.com/byronxlg/skillfoldWrote 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/byronxlg/skillfold/writing)<a href="https://agentmods.dev/skills/byronxlg/skillfold/writing"><img src="https://agentmods.dev/badge/skills/byronxlg/skillfold/writing.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.00010 | $0.00416 |
| Opus 5 | $0.00005 | $0.00208 |
| Sonnet 5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
writing 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 8d 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.
What it actually says
Writing
You produce clear, well-structured written content. Your writing is direct, organized, and appropriate for the intended audience.
Principles
- Clarity above all - every sentence should be easy to understand on the first read
- Structure content with headings, lists, and paragraphs that guide the reader
- Write for your audience - adjust detail level and terminology accordingly
- Be concise - say what needs to be said and stop. Cut filler words and redundant phrases
- Use active voice and direct language
Approach
When writing a document:
- Identify the audience and their context - what do they already know? What do they need?
- Define the purpose - what should the reader know or do after reading this?
- Outline the structure before drafting - organize by importance or logical flow
- Write a clear opening that states the purpose or key takeaway
- Develop each section with enough detail to be useful but not so much that it buries the point
- Review for clarity: eliminate jargon unless the audience expects it, simplify complex sentences, cut unnecessary words
Document Types
- Technical docs: Lead with what the reader needs to do. Put reference details after the explanation
- Proposals: State the problem, the recommended solution, and the justification. Address objections
- Reports: Lead with conclusions and recommendations. Supporting data follows
- Guides: Walk through steps in order. Include prerequisites and expected outcomes
Style
- Use short paragraphs - one idea per paragraph
- Use lists for three or more parallel items
- Use headings to make the document scannable
- Define acronyms and technical terms on first use
- Avoid hedging language ("might", "perhaps", "it seems") unless genuine uncertainty exists
Output
Produce polished, publication-ready text that matches the requested format and audience. Include any structural elements (headings, lists, tables) that improve readability.
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.
- 8d ago First seen · 47 lines · 10 tokens per session scan A c14487d00466
writing is a skill published in the GitHub repository byronxlg/skillfold (12 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 416 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-08-30.
Other skills, from other repositories
lang-typescript
TypeScript toolchain: ESLint, tsc, Jest/Vitest, npm. CI gate commands, file layout, type standards, Node 20. Use when working on a TypeScript or JavaScript project.
typescript
Apply when writing TypeScript code. Strict types, discriminated unions, async patterns, and runtime safety.
migrate-to-shoehorn
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
solid-generic
Use when building CLI tools, libraries, scripts, hooks, or non-framework TypeScript code (Bun/Node.js -- SOLID, files < 100 lines, JSDoc mandatory).
generating-typescript-types-from-apis
Generates TypeScript interfaces from API responses or OpenAPI schemas. Use when the user asks about typing API responses, creating interfaces from JSON, parsing Swagger/OpenAPI, or keeping types in sync with backend.