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 agentmods add skills/moasq/agentic-ship/writing-guidelinesnpx skills add moasq/agentic-ship --skill writing-guidelinesgit clone --depth 1 https://github.com/moasq/agentic-shipWrote 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/moasq/agentic-ship/writing-guidelines)<a href="https://agentmods.dev/skills/moasq/agentic-ship/writing-guidelines"><img src="https://agentmods.dev/badge/skills/moasq/agentic-ship/writing-guidelines.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 | $0.00068 | $0.01053 |
| Opus 5 | $0.00034 | $0.00526 |
| Sonnet 5 | $0.00014 | $0.00211 |
| Haiku 4.5 | $0.00007 | $0.00105 |
Grade A, and why
writing-guidelines 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 5d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing guidelines
Docs succeed because of hundreds of small decisions. This skill carries the Vercel docs
handbook (vendored under references/) and binds it to this stack: which rules apply
verbatim, which are replaced by house rules, and the order of the writing loop.
The writing loop
- Plan first. Before drafting a page, write five lines: overview, goal, audience, content plan, open questions. The goal takes a testable verb (configure, explain, debug). Pick one content type per page: tutorial, how-to, reference, conceptual, troubleshooting, or landing. One page does one job.
- Draft against the handbook.
references/guidelines.mdis the full rule set; apply everything the scope table below does not override. - Review with the checklist.
references/review-checklist.mdis a self-contained review prompt. Run it over the finished draft and report findings infile:lineform. It also names the AI-tell patterns to flag: summary-style transitions, spec-sheet voice, stop-start fragments, personified artifacts. - Humanize. Run the
humanizerskill over the final prose in embedded mode. It is the last pass, after content is settled, so it edits voice rather than facts.
What binds here, what does not
Most of the handbook transfers verbatim: active voice, direct address, imperative
steps, sentences under 20 words, sentence-case headings, descriptive subheadings,
summary-first pages and sections, acronyms spelled out on first use, list and code-block
discipline, descriptive snake_case placeholders, no em dashes, no banned words
(easy, simple, quick), no filler (very, just, really).
These upstream rules are Vercel product conventions and do not bind:
- Curly quotes and the
…ellipsis character: this stack writes plain markdown for terminals, GitHub, and diff review, and thehumanizerskill treats curly quotes as an AI tell. Straight quotes and three dots win. This is the one deliberate conflict between the two vendored sources, resolved here. meta.contentType,meta.navLabel,<Steps/>, non-breaking spaces, dashboard deep-link formats, the ACME demo account,vercel/examples, and model-string requirements: all specific to Vercel's docs platform. Declare the content type in the plan instead of frontmatter, and use the components this stack actually ships.- "Use only enterprise models" and PR-disclosure process rules: team policy for Vercel employees, recorded in the reference, not enforced here.
What ships with it
3 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.
- 5d ago First seen · 82 lines · 68 tokens per session scan A 7a1817efa7e4
writing-guidelines is a skill published in the GitHub repository moasq/agentic-ship (11 stars, last pushed 3d ago), licensed MIT. It adds 68 tokens to every session and 1,053 once invoked, about $0.0003 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…