Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jasonm4130/claude-skills/plugin install writing-artifactsWrote 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/readme)<a href="https://agentmods.dev/skills/jasonm4130/claude-skills/readme"><img src="https://agentmods.dev/badge/skills/jasonm4130/claude-skills/readme/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/readme"><img src="https://agentmods.dev/badge/skills/jasonm4130/claude-skills/readme.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.00113 | $0.01793 |
| Opus 5.5 | $0.00045 | $0.00717 |
| Sonnet 5.5 | $0.00023 | $0.00359 |
| Haiku 4.5 | $0.00011 | $0.00179 |
Grade A, and why
readme 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 16d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
readme
A README is read by a stranger deciding, in about thirty seconds, whether this project is for them. Everything in it must be true of the repository as it stands today, and the first screen must answer the stranger's questions before it answers the maintainer's. This skill gives the procedure for getting there and a checker for the parts a script can verify. For sentence-level prose, apply writing-artifacts:writing-artifacts as well.
It applies to a new README, a rewrite, an audit of an existing one, or a README change inside a pull request. It does not decide what the project is, capture screenshots, or pick a license. When one of those is missing, say so and leave the decision to the owner.
Stance
Say only what a reader could verify from the repository, and mark what you could not verify. A README that overclaims is worse than a short one: the reader trusts it once.
Procedure
1. Read before writing
Read the existing README, the manifest (package.json, pyproject.toml, Cargo.toml, .claude-plugin/plugin.json or equivalent), the CLI's own help output, .github/workflows/, the LICENSE file if any, and every doc the README links to. Note whether the repository is public or private (gh repo view --json visibility).
2. Build a fact inventory
Before drafting, list every fact the README will state, each with its source as file:line or the command whose output shows it:
- commands and their flags
- paths and file names
- numbers: versions, counts, ports, timeouts, defaults
- requirements: runtime and its version, OS, accounts, other tools
- what the project produces or shows
A fact with no source is marked unverified. Either find its source, run the command to confirm it, or leave it out. Never invent a command, flag, path or link because it is what such a project usually has.
3. Score the first screen
The first screen is what shows before scrolling: roughly the title, badges and first twenty lines. Score each item present, missing, or not applicable:
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.
- 16d ago First seen · 106 lines · 113 tokens per session scan A 7ec4e684f864
readme is a skill published in the GitHub repository jasonm4130/claude-skills (5 stars, last pushed 14d ago), licensed MIT. It adds 113 tokens to every session and 1,793 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-10-16.
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…