check-spelling

A project-specific spelling checker that uses cSpell, a tool that finds words it does not recognise in source files. It also describes how to add valid technical terms to the project dictionary.

In plain words
What is it for?
Use it to check changed source files, review misspellings, replace confirmed errors, or record legitimate project terms as accepted words.
Why use it?
It catches spelling mistakes while respecting the repository’s shared and folder-specific word lists.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/azure/azure-sdk-for-rust/check-spelling
Any agent
npx skills add Azure/azure-sdk-for-rust --skill check-spelling
Clone the repo
git clone --depth 1 https://github.com/Azure/azure-sdk-for-rust

Made for: Claude Code, Codex.

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 474 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00016 $0.00474
Opus 5 $0.00008 $0.00237
Sonnet 5 $0.00003 $0.00095
Haiku 4.5 $0.00002 $0.00047

Measured yesterday against content hash c9ac7353bd26, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

check-spelling 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 yesterday.

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.

.github/skills/check-spelling/SKILL.md · 55 lines

What it actually says

Spell checking

Usage

Get all staged and unstaged non-deleted files, then pipe them to the spell check script:

{ git diff --staged --name-only --diff-filter=d; git diff --name-only --diff-filter=d; } | sort -u | ./eng/common/spelling/Invoke-Cspell.ps1

Configuration

The root configuration is .vscode/cspell.json, and CI runs cSpell with this config via eng/common/spelling/Invoke-Cspell.ps1.

Each service directory (e.g., sdk/{service-directory}) or crate directory (e.g., sdk/{service-directory}/{crate-directory}) can have a .cspell.json that should import either a parent .cspell.json or .vscode/cspell.json from the root of the repo. Per-directory configs are loaded based on the paths of files being checked.

Fix spelling

Show a summary of the misspellings to the user. Prompt the user for which words should be replaced and which should be ignored.

For words that should be replaced, fix the misspellings directly in the source files. If you cannot confidently determine the correct spelling, ask the user.

For words that should be ignored, add them to the ignoreWords array in a .cspell.json file under sdk/{service-directory} or lower. If the file doesn't exist, create it with an import of either a parent .cspell.json or ../../.vscode/cspell.json from the root of the repo.

Example sdk/keyvault/.cspell.json:

{
  "import": [
    "../../.vscode/cspell.json"
  ],
  "ignoreWords": [
    "ciphertext",
    "purgeable"
  ]
}

Seldom used words can be ignored within the file they are used by adding an appropriate comment e.g.:

// cspell:ignore {word}

To disable cSpell for just the next line, use cspell:disable-next-line.

Testing

Run the same command again used to check spelling. All misspellings should be fixed.

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. yesterday First seen · 55 lines · 16 tokens per session scan A c9ac7353bd26

Subscribe to this mod's changes

check-spelling is a skill published in the GitHub repository Azure/azure-sdk-for-rust (885 stars, last pushed 3d ago), licensed MIT. It adds 16 tokens to every session and 474 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

dpg-migration

Migration logic for Azure SDK for .NET data-plane libraries migrating from AutoRest/Swagger to TypeSpec-based generation. Uses MCP tools from the generator-agent server for automated deterministic fixes.

Azure/azure-sdk-for-net · 41 tokens

csharp-azure-spector-coverage-gaps

Discovers and implements gaps in Spector test coverage for the Azure C# HTTP client emitter. Use when asked to find missing Spector scenarios, add Spector test coverage, or implement a specific Spector spec for the Azure C# emitter. Can also compare coverage between the Azure dashboard and the Standard (TypeSpec core)…

Azure/azure-sdk-for-net · 78 tokens

auto-build-repair

Headless, bounded repair of custom-code build failures in an already-generated Azure SDK PR. Thin wrapper over the shared azure-sdk-mcp:azsdkcustomizedcodeupdate engine in custom-code-only scope (editScope: CustomCode); the skill owns the iterate-until-green loop, capped by a per-language maxIterations read from…

Azure/azure-sdk-for-net · 149 tokens

azure-sdk-mgmt-pr-review

Review Azure SDK management-plane pull requests, check naming conventions, API compatibility, and code quality.

Azure/azure-sdk-for-net · 26 tokens

mgmt-review-comment-resolution

Resolve review comments on Azure management-plane .NET SDK PRs. Handles renaming types/properties, changing property types, and other API surface adjustments by updating TypeSpec client.tsp and regenerating.

Azure/azure-sdk-for-net · 46 tokens

mitigate-breaking-changes

Patterns and techniques for mitigating breaking changes during Azure management-plane SDK migration from Swagger/AutoRest to TypeSpec. Covers SDK-side customizations (partial classes, CodeGenType, CodeGenSuppress) and TypeSpec decorator customizations (clientName, access, markAsPageable, alternateType…

Azure/azure-sdk-for-net · 68 tokens