Borrowing it
Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/s-hiraoku/vscode-sidebar-terminal/main/.claude/skills/doc-consistency/SKILL.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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.
[](https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/doc-consistency)<a href="https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/doc-consistency"><img src="https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/doc-consistency/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.
<a href="https://agentmods.dev/skills/s-hiraoku/vscode-sidebar-terminal/doc-consistency"><img src="https://agentmods.dev/badge/skills/s-hiraoku/vscode-sidebar-terminal/doc-consistency.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00063 | $0.01377 |
| Opus 5 | $0.00032 | $0.00688 |
| Sonnet 5 | $0.00013 | $0.00275 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
doc-consistency 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Consistency Skill
This skill ensures project documentation accurately reflects the current implementation.
When to Use This Skill
- After implementing a new feature
- After fixing a bug that changes behavior
- Before creating a release
- When adding or modifying configuration options
- When adding or modifying keyboard shortcuts
- When updating architecture or patterns
- When reviewing documentation quality
Documentation Update Workflow
1. Identify Changed Components
After code changes, determine which documentation needs updates:
| Change Type | Documents to Update |
|---|---|
| New feature | README.md, CHANGELOG.md |
| Bug fix | CHANGELOG.md |
| Config change | README.md (Configuration), CHANGELOG.md |
| Shortcut change | README.md (Keyboard Shortcuts), CHANGELOG.md |
| Architecture change | CLAUDE.md, possibly domain CLAUDE.md files |
| WebView change | src/webview/CLAUDE.md, CLAUDE.md |
| Test pattern change | src/test/CLAUDE.md |
2. Update Documentation in Order
-
CHANGELOG.md - Always update first
- Add entry under
[Unreleased]section - Use correct section (Added/Changed/Fixed/etc.)
- Include issue/PR number if applicable
- Add entry under
-
README.md - If user-visible changes
- Features table if new feature
- Configuration section if settings changed
- Keyboard Shortcuts if bindings changed
-
CLAUDE.md - If development process affected
- Commands section if new npm scripts
- Architecture section if patterns changed
- Guidelines if best practices updated
-
Domain-specific docs - If specialized area changed
- src/webview/CLAUDE.md for WebView changes
- src/test/CLAUDE.md for testing changes
3. Verify Consistency
Run verification checks from references/verification-checklist.md:
# Version check
node -p "require('./package.json').version"
# Commands check
node -p "require('./package.json').contributes.commands.map(c => c.command).join('\n')"
# Config check
node -p "Object.keys(require('./package.json').contributes.configuration.properties).join('\n')"
What ships with it
3 files 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.
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.
- 9d ago First seen · 225 lines · 63 tokens per session scan A 330b6ae39f77
doc-consistency is a skill published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 1,377 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-09-01.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.