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 EzraApple/skills-init --skill writing-skillsgit clone --depth 1 https://github.com/EzraApple/skills-initWrote 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/ezraapple/skills-init/writing-skills)<a href="https://agentmods.dev/skills/ezraapple/skills-init/writing-skills"><img src="https://agentmods.dev/badge/skills/ezraapple/skills-init/writing-skills/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/ezraapple/skills-init/writing-skills"><img src="https://agentmods.dev/badge/skills/ezraapple/skills-init/writing-skills.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.00026 | $0.00458 |
| Opus 5.5 | $0.00010 | $0.00183 |
| Sonnet 5.5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
writing-skills 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 18d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write useful skills
Assume the agent can already plan, code, and check its work. Keep guidance that changes a decision, supplies missing operational knowledge, or prevents a demonstrated failure. Delete generic encouragement and duplicated process.
Before adding a skill, define its intended outcome, a realistic request it improves, and a nearby request it should leave alone. Prefer an existing skill's reference for a specialized variant. Use code, types, or lint for mechanically enforceable rules. Keep broad project conventions in the repository's existing agent guidance.
Before revising, read the existing skill and its linked resources. Identify the mechanism, constraints, and outputs that make it useful. Preserve them when shortening it, or make the intended behavior change explicit.
Make discovery precise
Use name and description in YAML frontmatter. The name should match the
directory. Describe the capability and actual triggering task briefly. Add an
exclusion only when it prevents likely misrouting; avoid lists of loosely related
keywords. Preserve supported metadata and the user's invocation preferences.
Keep the main instructions self-contained when they are short. For distinct operating modes, link focused references and say when to read each. Do not move text out merely to force the agent to read it all through links. Put repeatable mechanics in scripts only when they earn their maintenance cost.
Use .agents/skills when this package owns project installation. Respect an
existing source of truth elsewhere; do not create competing copies or rewrite
unrelated host configuration.
Check what changed
Validate metadata, local links, and any executable helpers. A linter proves structure, not usefulness. Review the instructions for clear scope and duplicated guidance.
For a new skill or a changed description or reference route, compare a realistic request that should use it with a nearby request that should not. Trace which instructions or references each request would reach.
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.
- 18d ago Changed · -195 lines · -9 tokens per session c968734b3f3b
- 2mo ago First seen · 245 lines · 35 tokens per session scan A 8aecc43b71f6
writing-skills is a skill published in the GitHub repository EzraApple/skills-init (2 stars, last pushed 19d ago), licensed MIT. It adds 26 tokens to every session and 458 once invoked, about $0.0001 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
oma-scholar
Search academic literature and generate, validate, or compare Knows paper sidecars. Use for claim/evidence analysis and literature synthesis.
pkf-writing
Author, update, convert, validate, persist, and render PKF (.pkf) content through message-inline, Library Asset, or Memory Page carriers. Use for structured reports, knowledge pages, delivery cards, or any .pkf body. NOT for recall, memory-graph placement, or curation decisions — those belong to the memory skill.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
render-3d-product-showcase
Assemble a premium 3D product-showcase ad from a config — four beat clips (an orbiting hero rotation, a macro push-in, a physics reveal, a typographic close) normalized to the chosen backdrop colour, hard-concatenated in order, closed on a deterministic Playwright brand end card, and mixed under one instrumental bed…
render-airdrop-carousel
Assemble a viral iOS "AirDrop" notification-carousel video ad (≈6–8s, 9:16) from a brand line plus 6–16 real product photos — a native AirDrop share-sheet card ("Brand would like to share a · Decline / Accept") springs up and its preview window CYCLES through the products, landing on a range/lineup payoff with an…
email-lifecycle-flow-writer
Step of the email-lifecycle playbook: writes one lifecycle flow as a build sheet for the brand's email tool, every message finished in the brand voice. Run email-lifecycle instead; not for direct use.