docs-standards

docs-standards is a skill for Claude Code, Codex from DanWahlin/ai-agent-board. It costs 13 tokens per session (530 once invoked), scanned A, a copy of docs-standards, MIT.

A documentation-writing skill based on the Microsoft Style Guide and additional Squad conventions.

In plain words
What is it for?
Use it when adding or editing documentation pages. It can guide practical prompts, warnings, short paragraphs, lists, tables, and related-page links.
Why use it?
It helps keep documentation consistent, readable, and easy to find by enforcing conventions for headings, voice, tense, structure, formatting, and links.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when adding or editing documentation pages. It can guide practical prompts, warnings, short paragraphs, lists, tables, and related-page links.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/danwahlin/ai-agent-board/docs-standards
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 DanWahlin/ai-agent-board --skill docs-standards
Clone the repo
git clone --depth 1 https://github.com/DanWahlin/ai-agent-board

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 docs-standards

README.md
[![agentmods](https://agentmods.dev/badge/skills/danwahlin/ai-agent-board/docs-standards.svg)](https://agentmods.dev/skills/danwahlin/ai-agent-board/docs-standards)
Your own site
<a href="https://agentmods.dev/skills/danwahlin/ai-agent-board/docs-standards"><img src="https://agentmods.dev/badge/skills/danwahlin/ai-agent-board/docs-standards.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 530 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 100% 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.00013 $0.00530
Opus 5 $0.00006 $0.00265
Sonnet 5 $0.00003 $0.00106
Haiku 4.5 $0.00001 $0.00053

Measured 8d ago against content hash 49a99de5527e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

docs-standards 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 8d 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

100% identical to docs-standards — 0 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.

.squad/templates/skills/docs-standards/SKILL.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context

Squad documentation follows the Microsoft Style Guide with Squad-specific conventions. Consistency across docs builds trust and improves discoverability.

Patterns

Microsoft Style Guide Rules

  • Sentence-case headings: "Getting started" not "Getting Started"
  • Active voice: "Run the command" not "The command should be run"
  • Second person: "You can configure..." not "Users can configure..."
  • Present tense: "The system routes..." not "The system will route..."
  • No ampersands in prose: "and" not "&" (except in code, brand names, or UI elements)

Squad Formatting Patterns

  • Scannability first: Paragraphs for narrative (3-4 sentences max), bullets for scannable lists, tables for structured data
  • "Try this" prompts at top: Start feature/scenario pages with practical prompts users can copy
  • Experimental warnings: Features in preview get callout at top
  • Cross-references at bottom: Related pages linked after main content

Structure

  • Title (H1)Warning/calloutTry this codeOverviewHRContent (H2 sections)

Test Sync Rule

  • Always update test assertions: When adding docs pages to features/, scenarios/, guides/, update corresponding EXPECTED_* arrays in test/docs-build.test.ts in the same commit

Examples

Correct:

# Getting started with Squad

> ⚠️ **Experimental:** This feature is in preview.

Try this:
\`\`\`bash
squad init
\`\`\`

Squad helps you build AI teams...

---

## Install Squad

Run the following command...

Incorrect:

# Getting Started With Squad  // Title case

Squad is a tool which will help users... // Third person, future tense

You can install Squad with npm & configure it... // Ampersand in prose

Anti-Patterns

  • Title-casing headings because "it looks nicer"
  • Writing in passive voice or third person
  • Long paragraphs of dense text (breaks scannability)
  • Adding doc pages without updating test assertions
  • Using ampersands outside code blocks

Read the full file on GitHub · 72 lines

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. 8d ago First seen · 72 lines · 13 tokens per session scan A 49a99de5527e

Subscribe to this mod's changes

docs-standards is a skill published in the GitHub repository DanWahlin/ai-agent-board (57 stars, last pushed 14d ago), licensed MIT. It adds 13 tokens to every session and 530 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to docs-standards, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

foundry-config-setup

Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.

microsoft/agent-framework · 65 tokens

haiku

When writing a haiku for this bot, follow these conventions.

agno-agi/agno · 0 tokens

deploy-docker-compose

Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…

omnigent-ai/omnigent · 84 tokens

fastapi-router-py

Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.

microsoft/skills · 46 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

mochi-remind

Handle due reminders — notify the user with natural language and mark them done.

kirodotdev/KiroCrew · 20 tokens