agentmods.dev

format_markdown

A set of rules for keeping Markdown files consistent and valid. Markdown is a plain-text format commonly used for documentation.

In plain words
What is it for?
Use it when creating or editing Markdown to check headings, lists, tables, code blocks, links, images, spacing, and file endings.
Why use it?
It catches layout and style problems that make documentation harder to read or fail automated checks.

Skill for Claude CodeCodex

38 3d ago A scan 62 tokens original MIT
View the source file theafh/ai-modules
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/theafh/ai-modules/format_markdown
Any agent
npx skills add theafh/ai-modules --skill format_markdown
Clone the repo
git clone --depth 1 https://github.com/theafh/ai-modules

Made for: Claude Code, Codex.

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 338 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.00062 $0.00338
Opus 5 $0.00031 $0.00169
Sonnet 5 $0.00012 $0.00068
Haiku 4.5 $0.00006 $0.00034

Measured 2d ago against content hash 1c822d6651a7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

format_markdown 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 2d 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.

plugins/ai_dev/skills/format_markdown/SKILL.md · 31 lines

What it actually says

format_markdown

Linting Compliance

  • Blank lines: One around headings, lists, tables, code blocks
  • Single newline: File must end with exactly one newline
  • No multiple blanks: Maximum one consecutive blank line
  • Consistent bullets: Use - for all unordered lists
  • Fenced code: Always use language identifier
  • Table alignment: Use :---: for center, :--- for left, ---: for right
  • Header levels: Don't skip levels (H1 → H2 → H3, not H1 → H3)
  • List indentation: 2 spaces for nested items
  • List marker spacing: Use 1 space after list markers
  • No bare URLs: Wrap in angle brackets or use reference links
  • No trailing punctuation: In headers

Best Practices

  • Descriptive links: Meaningful text, not "click here"
  • Alt text: Always for images
  • Consistent emphasis: **bold** and *italic* only
  • Table headers: Always include
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. 2d ago First seen · 31 lines · 62 tokens per session scan A 1c822d6651a7

Subscribe to this mod's changes

format_markdown is a skill published in the GitHub repository theafh/ai-modules (38 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 338 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-30.

Writing and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens