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 jasonm4130/claude-skills --skill writing-artifactsgit clone --depth 1 https://github.com/jasonm4130/claude-skillsWrote 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/jasonm4130/claude-skills/writing-artifacts)<a href="https://agentmods.dev/skills/jasonm4130/claude-skills/writing-artifacts"><img src="https://agentmods.dev/badge/skills/jasonm4130/claude-skills/writing-artifacts/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/jasonm4130/claude-skills/writing-artifacts"><img src="https://agentmods.dev/badge/skills/jasonm4130/claude-skills/writing-artifacts.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.00115 | $0.01039 |
| Opus 5.5 | $0.00046 | $0.00416 |
| Sonnet 5.5 | $0.00023 | $0.00208 |
| Haiku 4.5 | $0.00012 | $0.00104 |
Grade A, and why
writing-artifacts 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 2mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
writing-artifacts
A durable artifact has readers you will never meet, arriving with zero conversation context, often skimming, sometimes another agent. Write for that reader. This skill is a system to write toward, not a list of things to avoid: supply the right structure and the slop has nowhere to live.
Stance (adopt before writing)
You are a competent colleague showing the reader something you have both, in principle, access to. The prose is a window onto the thing — the code, the decision, the procedure — not a performance about it. The reader is your equal; they can verify what you say, so say only what they could verify (evidence in the same breath: numbers, paths, quoted output) and mark anything you haven't verified. Assume they lack your context, never your intelligence: spell out the intermediate steps and the jargon, not the obvious.
Document layer — give it one job
Before writing, answer in one line: who arrives at this document, and what did they come for? Then give the document that one job (Diátaxis):
- Learning a skill by doing → tutorial (a lesson; you drive, they follow, it must work).
- Getting a task done now → how-to (steps to a goal; they're at work, respect that).
- Looking something up while working → reference (facts, structured for lookup, no digressions).
- Understanding why, away from the keyboard → explanation (discursive, context, trade-offs).
When one document must serve two jobs (a README usually must), separate the jobs into sections rather than blending sentence-by-sentence — mixed types bleed and serve neither reader. Use the types as a compass, not a filing system; don't scaffold empty sections.
Order the whole document bottom-line-first: purpose and outcome in the first paragraph, general before exceptions, background last. A good README's first paragraph lets most readers stop reading, satisfied.
Paragraph layer
One point per paragraph, stated in the first sentence; the rest is support. In procedures: one action per step, condition before command ("If the build is red, do not deploy" — never the reverse).
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.
- 2mo ago First seen · 54 lines · 115 tokens per session scan A 74b28e087621
writing-artifacts is a skill published in the GitHub repository jasonm4130/claude-skills (5 stars, last pushed 14d ago), licensed MIT. It adds 115 tokens to every session and 1,039 once invoked, about $0.0005 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
nkz-taste
Design and build product UI with taste, for native mobile (iOS-first, Expo / React Native) and web (products, landing pages). Supports named styles with exact visual contracts and reusable layouts. Covers the product decision (what the screen is for, what the one action is, what to cut), the craft floor (four states…
corpus
Worked examples of bad and corrected Claude Code chat output. Use when a reply is about to run long, when unsure whether a sentence is decoration or information, when a status update is forming, or when the user says the output is too long, too corporate, full of jargon, or reads like AI. Also use when writing or…
sxo
Search Experience Optimization (SXO), the bridge between SEO and UX/CRO. Audits the journey from the SERP click to the on-page goal: click-through factors (title, meta, rich results), then post-click signals that keep users and drive conversions: above-the-fold relevance and intent match, page speed / Core Web Vitals…
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
critical-code-reviewer
Rigorously review code or pull requests for correctness, security, accessibility, maintainability, tests, and edge cases. Use when users request a critical code review, want a guided walkthrough of findings, need implementer-facing feedback, or want to prepare, create, or submit a GitHub pull request review.
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…