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 agentmods add skills/nickcrew/claude-cortex/doc-claim-validatornpx skills add NickCrew/Claude-Cortex --skill doc-claim-validatorgit clone --depth 1 https://github.com/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/doc-claim-validator)<a href="https://agentmods.dev/skills/nickcrew/claude-cortex/doc-claim-validator"><img src="https://agentmods.dev/badge/skills/nickcrew/claude-cortex/doc-claim-validator.svg" alt="Measured on agentmods" 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 | $0.00061 | $0.03055 |
| Opus 5 | $0.00030 | $0.01528 |
| Sonnet 5 | $0.00012 | $0.00611 |
| Haiku 4.5 | $0.00006 | $0.00305 |
Grade A, and why
doc-claim-validator 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.
How it starts
The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Claim Validator
Verify that what documentation says is actually true by extracting testable claims
and checking them against the codebase. Complements doc-maintenance (which handles
structural health) by handling semantic accuracy.
When to Use
- After significant code changes (refactors, renames, API changes)
- Before releases — catch docs that describe removed or changed behavior
- When onboarding devs report "the docs are wrong"
- As a periodic trust audit on project documentation
- After running
doc-maintenanceto go deeper than structural checks
Quick Reference
| Resource | Purpose | Load when |
|---|---|---|
scripts/extract_claims.py |
Deterministic claim extraction from markdown | Always (Phase 1) |
scripts/verify_claims.py |
Automated verification against codebase | Always (Phase 2) |
references/claim-taxonomy.md |
Full taxonomy of claim types with examples | Triaging unclear claims |
Workflow Overview
Phase 1: Extract → Pull verifiable claims from docs (deterministic script)
Phase 2: Verify → Check claims against codebase (automated + AI)
Phase 3: Report → Classify failures by severity and type
Phase 4: Remediate → Fix or flag broken claims
Phase 1: Extract Claims
Run the extraction script to parse all markdown files and pull out verifiable assertions:
python3 skills/doc-claim-validator/scripts/extract_claims.py [--json] [--root PATH] [--scope docs|manual|all]
The script extracts these claim types from markdown:
| Type | What it captures | Example in docs |
|---|---|---|
file_path |
Inline code matching file path patterns | `src/auth/login.ts` |
command |
Code blocks or inline code with shell commands | `npm run build` |
code_ref |
Function, class, method references in inline code | `authenticate()` |
import |
Import/require statements in code blocks | import { Router } from 'express' |
config |
Configuration keys, env vars, settings | `MAX_RETRIES=3` |
url |
External links (http/https) | [docs](https://example.com) |
architectural |
Verb-anchored prose claims about technology, integrations, or architectural patterns | "Uses Redis for caching", "follows the actor model", "delegated to Auth0" |
dependency |
Package/library name claims | "Uses Redis for caching" |
behavioral |
Assertions about what code does | "The system retries 3 times" |
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.
- yesterday First seen · 305 lines · 61 tokens per session scan A 63d32f6d0689
doc-claim-validator is a skill published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 3,055 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-03.
Other skills, from other repositories
documentation-verification
Validate documentation before merging - check completeness, broken links, code example accuracy, and factual correctness. Use when reviewing docs for quality gates or running pre-merge doc validation.
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
requesting-code-review
Pre-commit review: security scan, quality gates, auto-fix.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
aap-lint
Skill "aap-lint" from automateyournetwork/netclaw, covering ansible lint operations, mcp server, available tools (9), key concepts and workflow: pre-deployment playbook validation.
verification-gates
Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step…