visual-standards

visual-standards is a skill for Claude Code, Codex from littlebearapps/pitchdocs. It costs 56 tokens per session (753 once invoked), scanned A, original, MIT.

A set of visual rules for repository documentation, especially READMEs with headings, tables of contents, callouts, screenshots, and images. It covers details such as heading icons, screenshot dimensions, captions, shadows, and image optimisation.

In plain words
What is it for?
Use it when creating or editing a README that includes visual sections, screenshots, image links, or other formatted presentation elements.
Why use it?
Documentation with screenshots and other visual elements can become inconsistent or difficult to scan. These rules provide a shared format for presenting those elements.

Skill for Claude CodeCodex

Part of the pitchdocs plugin — 16 skills, 15 commands, 4 agents shipped together

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/littlebearapps/pitchdocs/visual-standards
Any agent
npx skills add littlebearapps/pitchdocs --skill visual-standards
Clone the repo
git clone --depth 1 https://github.com/littlebearapps/pitchdocs

Made for: Claude Code, Codex.

Or install pitchdocs, the plugin that ships this one along with the rest of its 16 skills, 15 commands, 4 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/littlebearapps/pitchdocs/visual-standards.svg)](https://agentmods.dev/skills/littlebearapps/pitchdocs/visual-standards)
Your own site
<a href="https://agentmods.dev/skills/littlebearapps/pitchdocs/visual-standards"><img src="https://agentmods.dev/badge/skills/littlebearapps/pitchdocs/visual-standards.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 753 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.00056 $0.00753
Opus 5 $0.00028 $0.00377
Sonnet 5 $0.00011 $0.00151
Haiku 4.5 $0.00006 $0.00075

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

Security

Grade A, and why

visual-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 4d 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.

.claude/skills/visual-standards/SKILL.md · 74 lines

How it starts

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

Visual Standards

Emoji Heading Prefixes

Use a single emoji before each H2 heading to create visual anchors when scrolling.

Pattern: ## {emoji} Section Title

Recommended emoji by section type:

Section Type Emoji Example
Quick start / Getting started ## ⚡ Quick start
Why / Value proposition 💡 ## 💡 Why ProjectName?
Features 🎯 ## 🎯 Features
Commands / API / Usage 🤖 ## 🤖 Commands
Configuration ⚙️ ## ⚙️ Configuration
Requirements / Prerequisites 📦 ## 📦 Requirements
Documentation links 📚 ## 📚 Documentation
Contributing 🤝 ## 🤝 Contributing
Licence / License 📄 ## 📄 Licence
Security 🔒 ## 🔒 Security
Integrations / Plugins 🔌 ## 🔌 Integrations
How it compares ⚖️ ## ⚖️ How it compares
Roadmap 🗺️ ## 🗺️ Roadmap
What it does / Use cases 🚀 ## 🚀 What ProjectName Does

Rules:

  • One emoji per heading — never two
  • Use the same emoji consistently for the same section type across projects
  • Skip emoji prefixes for READMEs under 5 sections

Horizontal Rules as Section Separators

Use --- between major H2 sections to create visual breathing room (especially in 200+ line READMEs).

When to use: After hero/badge section, after TOC, between H2 sections, before licence/footer. When to skip: Between H3 subsections, in short documents (under 150 lines), in non-README files.

Table of Contents with Emoji Anchors

GitHub and GitLab strip the emoji character but retain the leading hyphen. Bitbucket prefixes all heading anchors with markdown-header- — load the platform-profiles skill when targeting Bitbucket.

- [Quick start](#-quick-start)
- [Why ProjectName?](#-why-projectname)
- [Features](#-features)
- [Configuration](#%EF%B8%8F-configuration)

Include a TOC for READMEs with 7+ sections.

Bold Inline Callouts

For brief warnings, tips, and notes, use bold inline callouts rather than GitHub-specific [!NOTE] syntax (which breaks on npm and PyPI).

Read the full file on GitHub · 74 lines

Files

What ships with it

1 file 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.

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. 4d ago First seen · 74 lines · 56 tokens per session scan A 0cdf180f4aab

Subscribe to this mod's changes

visual-standards is a skill published in the GitHub repository littlebearapps/pitchdocs (8 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 753 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.