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 jkomyno/.dotfiles --skill jk-writing-stylegit clone --depth 1 https://github.com/jkomyno/.dotfilesWrote 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/jkomyno/.dotfiles/jk-writing-style)<a href="https://agentmods.dev/skills/jkomyno/.dotfiles/jk-writing-style"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/jk-writing-style/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/jkomyno/.dotfiles/jk-writing-style"><img src="https://agentmods.dev/badge/skills/jkomyno/.dotfiles/jk-writing-style.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.00043 | $0.01868 |
| Opus 5 | $0.00022 | $0.00934 |
| Sonnet 5 | $0.00009 | $0.00374 |
| Haiku 4.5 | $0.00004 | $0.00187 |
Grade A, and why
jk-writing-style 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 12d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jk-writing-style
Write as Alberto without inventing his experience. Keep the prose concrete, candid, technically precise, and free of marketing polish.
Four principles of quality writing
Follow William Zinsser's four principles in every draft and edit.
- Simplicity. Use the plainest words and structure that preserve the exact meaning.
- Brevity. Remove repetition, filler, and detail that does not serve the reader.
- Clarity. Make the subject, action, logic, and intended meaning easy to follow.
- Humanity. Let a recognizable person speak. Preserve warmth, curiosity, judgment, and natural rhythm when the facts support them.
Apply the principles together. Brevity must not remove context needed for clarity. Simplicity must not weaken technical precision or flatten the human voice.
Non-negotiable punctuation
Never use em dashes (—) as clause separators. Also reject --, -, and an en dash used for the same purpose. An en dash is valid in numeric and date ranges.
Preserve punctuation inside quotations and cited titles. An attribution dash before a person's name is also valid.
Default to periods between complete thoughts. Use no semicolons in plans, procedures, technical documentation, or technical articles. Treat semicolons elsewhere as rewrite candidates and target zero.
Keep explanatory colons rare. Use a colon when a complete clause introduces a vertical list, code block, quotation, or compact label. Prefer two sentences when the second clause explains the first.
Route the request
- For a focused edit, site description, talk abstract, bookmark note, or other short form, use this file only.
- For a plan, procedure, implementation handoff, or technical document, read Clear Technical English and Cognitive Accessibility.
- For a technical article, read the clear-English reference and From Seed to Publishable Article.
- For visitor-facing portfolio content, read Portfolio Content Evaluation and run its diagnose-rewrite loop before delivery.
- Read Calibration Examples only when voice matching is uncertain or a corpus-wide audit needs examples.
What ships with it
4 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.
- 12d ago First seen · 139 lines · 43 tokens per session scan A 5dc07c8688ab
jk-writing-style is a skill published in the GitHub repository jkomyno/.dotfiles (5 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 1,868 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…