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.
npx skills add mishahanin/heading-os --skill validategit clone --depth 1 https://github.com/mishahanin/heading-osWrote 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/mishahanin/heading-os/validate)<a href="https://agentmods.dev/skills/mishahanin/heading-os/validate"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/validate/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/mishahanin/heading-os/validate"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/validate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00039 | $0.01416 |
| Opus 5 | $0.00019 | $0.00708 |
| Sonnet 5 | $0.00008 | $0.00283 |
| Haiku 4.5 | $0.00004 | $0.00142 |
Grade A, and why
validate 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.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Validate
Fact-check content against the 31C DataStore — the source-of-truth repository of authoritative original documents.
Variables
$ARGUMENTS— The content to validate. Either paste the draft text directly, or provide a file path to read.
Instructions
1. Load the Content
If $ARGUMENTS is a file path, read the file first. Otherwise, treat it as the draft text to validate.
2. Read the DataStore Index
Read datastore/INDEX.md to see what source documents are available.
3. Extract Claims
Scan the provided content and extract every factual claim:
Explicit claims:
- Numbers (team size, revenue, market data, percentages, pricing, performance specs)
- Names (people, companies, partners, products, titles/roles)
- Dates (founding, launches, events, milestones, timelines)
- Technical claims (capabilities, architecture, performance, specifications)
- Market claims (TAM, growth rates, market share, competitive positioning)
- Partnership claims (territories, terms, relationships, scope)
- Financial claims (valuations, funding amounts, deal economics, pricing)
Implicit claims:
- Superlatives and comparisons ("fastest," "first," "only," "leading")
- Attributed quotes or statistics ("according to Mordor Intelligence...")
- Implied uniqueness or exclusivity ("no other vendor offers...")
4. Validate Against Sources
For each claim, validate using this source hierarchy (highest authority first):
- DataStore — Read relevant source documents (PDFs up to 20 pages, or
-extract.mdcompanions for binary files) - context/ files — Cross-reference with current-data.md, business-info.md, pipeline.md, etc.
- reference/ files — Check market intelligence, competitive data, strategic frameworks
If sources conflict: DataStore wins over context/, which wins over reference/.
5. Assess Risk Level
For each unverified or contradicted claim, assign a risk level:
| Risk | When to Apply |
|---|---|
| High | Financial figures, legal claims, investor-facing data, partner terms, performance specs cited to prospects, pricing |
| Medium | Team size, timelines, market data, competitive comparisons, customer claims |
| Low | Qualitative descriptions, internal-only references, general positioning language |
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.
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.
- 8d ago First seen · 158 lines · 39 tokens per session scan A fb93376ccfc5
validate is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,416 once invoked, about $0.0002 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-03.
Other skills, from other repositories
shogun-bloom-config
An interactive wizard that creates model-routing settings from your AI subscription choices. Model routing decides which available model handles each kind of task.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
shogun-model-list
A reference table of AI command-line tools, their available models, subscription requirements, and maximum Bloom capability levels. Bloom's Taxonomy is a scale describing thinking tasks, from remembering information to creating new designs.
shogun-model-switch
A live-switching tool for changing which command-line AI agent, model, and reasoning mode is running. It updates settings, restarts the agent, and refreshes the displayed session information.
shogun-readme-sync
A skill that compares an English README with its Japanese counterpart and brings them back into alignment. A README is the project document that explains what the software is and how to use it.
shogun-agent-status
A skill that shows whether the agents in a multi-agent Japanese feudal-themed team are working, waiting, missing, or assigned tasks. It combines terminal session status, task files, and unread messages.