writing-guidelines

writing-guidelines is a skill for Claude Code, Codex from robotostudio/turbo-start-sanity. It costs 48 tokens per session (270 once invoked), scanned A, a copy of web-design-guidelines, MIT.

A writing-review skill that checks documentation and prose against the Writing Guidelines handbook. It reports problems in a concise file-and-line format.

In plain words
What is it for?
Use it to review documentation, audit tone, or check files against the handbook. It fetches the latest guidelines before each review.
Why use it?
It helps find style and voice issues that are easy to miss during editing.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to review documentation, audit tone, or check files against the handbook. It fetches the latest guidelines before each review.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/robotostudio/turbo-start-sanity/writing-guidelines
Install

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.

Any agent
npx skills add robotostudio/turbo-start-sanity --skill writing-guidelines
Clone the repo
git clone --depth 1 https://github.com/robotostudio/turbo-start-sanity

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for writing-guidelines

README.md
[![agentmods](https://agentmods.dev/badge/skills/robotostudio/turbo-start-sanity/writing-guidelines/github.svg)](https://agentmods.dev/skills/robotostudio/turbo-start-sanity/writing-guidelines)
Your own site
<a href="https://agentmods.dev/skills/robotostudio/turbo-start-sanity/writing-guidelines"><img src="https://agentmods.dev/badge/skills/robotostudio/turbo-start-sanity/writing-guidelines/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.

agentmods 80×15 button for writing-guidelines

Your own site · 80×15
<a href="https://agentmods.dev/skills/robotostudio/turbo-start-sanity/writing-guidelines"><img src="https://agentmods.dev/badge/skills/robotostudio/turbo-start-sanity/writing-guidelines.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 270 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 77% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.00270
Opus 5 $0.00024 $0.00135
Sonnet 5 $0.00010 $0.00054
Haiku 4.5 $0.00005 $0.00027

Measured 11d ago against content hash 89a5f5811932, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 11d 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.

Origin

This is a copy

77% identical to web-design-guidelines — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/writing-guidelines/SKILL.md · 40 lines

What it actually says

Writing Guidelines

Review files for compliance with Writing Guidelines.

How It Works

  1. Fetch the latest guidelines from the source URL below
  2. Read the specified files (or prompt user for files/pattern)
  3. Check against all rules in the fetched guidelines
  4. Output findings in the terse file:line format

Guidelines Source

Fetch fresh guidelines before each review:

https://raw.githubusercontent.com/vercel-labs/writing-guidelines/main/command.md

Use WebFetch to retrieve the latest rules. The fetched content contains all the rules and output format instructions.

Usage

When a user provides a file or pattern argument:

  1. Fetch guidelines from the source URL above
  2. Read the specified files
  3. Apply all rules from the fetched guidelines
  4. Output findings using the format specified in the guidelines

If no files specified, ask the user which files to review.

Changes

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.

  1. 11d ago First seen · 40 lines · 48 tokens per session scan A 89a5f5811932

Subscribe to this mod's changes

writing-guidelines is a skill published in the GitHub repository robotostudio/turbo-start-sanity (176 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 270 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 77% identical to web-design-guidelines, differing in 10 lines, and is treated as a copy.

Related

Other skills, from other repositories

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit calls, or resolve the link-prefetch-partial and instant-shell-url-data…

sanity-io/next-sanity · 92 tokens

sanity-live-cache-components

Integrates Sanity Live with Next.js Cache Components in next-sanity v13+ apps. Sets up sanityFetch, a shared cachedSanity 'use cache' boundary, , Visual Editing, Presentation Tool, draft mode handling, and the three-layer (Page/Dynamic/Cached) component pattern with explicit perspective/stega prop-drilling. Sequences…

sanity-io/next-sanity · 155 tokens

pnpm

Node.js package manager with strict dependency resolution. Use when running pnpm specific commands, configuring workspaces, or managing dependencies with catalogs, patches, or overrides.

sanity-io/next-sanity · 35 tokens

gcss-v3-site-framework

Initialize, adapt, audit, upgrade, or downgrade projects built from gcss-v3-site-framework. Use for A1/A2/B/C delivery profiles, static-brand/cms-brand/retail setup, Astro and Sanity page models, the C Retail Catalog & Content Foundation with read-only Shopify catalog mapping, Cloudflare Worker routes, project…

ZUnfurl/zunfurl · 88 tokens

grill-with-docs

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

sanity-io/next-sanity · 57 tokens

find-skills

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

sanity-io/next-sanity · 67 tokens