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 wahidyankf/ose-public --skill docs-validating-factual-accuracygit clone --depth 1 https://github.com/wahidyankf/ose-publicWrote 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/wahidyankf/ose-public/docs-validating-factual-accuracy)<a href="https://agentmods.dev/skills/wahidyankf/ose-public/docs-validating-factual-accuracy"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-validating-factual-accuracy/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/wahidyankf/ose-public/docs-validating-factual-accuracy"><img src="https://agentmods.dev/badge/skills/wahidyankf/ose-public/docs-validating-factual-accuracy.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.00076 | $0.00820 |
| Opus 5.5 | $0.00030 | $0.00328 |
| Sonnet 5.5 | $0.00015 | $0.00164 |
| Haiku 4.5 | $0.00008 | $0.00082 |
Grade A, and why
docs-validating-factual-accuracy 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Factual Validation Methodology Skill
Purpose
This Skill provides a universal methodology for verifying factual correctness in technical documentation, educational content, and code examples using WebSearch and WebFetch tools.
When to use this Skill:
- Verifying command syntax and flags
- Checking version numbers and compatibility
- Validating code examples compile/run correctly
- Confirming API methods and signatures
- Verifying external claims and references
- Classifying confidence levels for documentation
- Maintaining factual accuracy in tutorials
Core Concepts
What is Factual Validation?
Factual validation is the systematic process of verifying objective, verifiable claims in documentation against authoritative sources using web search and retrieval tools.
Validates:
- Command syntax (bash, npm, git commands)
- Software version numbers
- API method names and signatures
- Code example correctness
- Configuration file formats
- Library/package availability
- External factual claims
Does NOT validate:
- Subjective quality assessments
- Narrative flow or writing style
- Architectural decisions or opinions
- Future predictions or speculation
The Four Confidence Classifications
See The Four Confidence Classifications for the full
[Verified] / [Error] / [Outdated] / [Unverified] definitions with examples of each.
Validation Workflow
See Step-by-Step Validation Workflow for the six-step process from identifying claims through documenting a finding, with a worked npm-flag example.
Source Prioritization
See Source Prioritization for the four-tier source hierarchy — official documentation, package registries, official release notes, and well-maintained community sources — with examples and when to use each.
Common Validation Patterns
See Common Validation Patterns for four worked patterns: command syntax, version number, code example, and API method validation.
What ships with it
9 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.
- README.md 693 B
- reference/checker-integration.md 3.0 KB
- reference/common-validation-patterns.md 2.7 KB
- reference/confidence-classifications.md 1.1 KB
- reference/mistakes-and-best-practices.md 2.1 KB
- reference/README.md 944 B
- reference/source-prioritization.md 1.8 KB
- reference/update-frequency-and-metadata.md 1.0 KB
- reference/validation-workflow.md 1.8 KB
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.
- 2d ago First seen · 97 lines · 76 tokens per session scan A 9e5dff65a868
docs-validating-factual-accuracy is a skill published in the GitHub repository wahidyankf/ose-public (12 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 820 once invoked, about $0.0003 per session on Opus 5.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-10-14.
Other skills, from other repositories
turborepo
Configure and troubleshoot Turborepo repositories. Use when working with turbo.json, task pipelines, caching, Remote Cache, the turbo CLI, filtering, environment variables, package boundaries, monorepo structure, or CI workflows.
nx-plugin-for-aws
Scaffold and build cloud-native applications on AWS using @aws/nx-plugin generators. Use when the user wants to create workspaces, generate projects, or scaffold infrastructure with the Nx Plugin for AWS.
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…
investigate-cloudflare
Investigate deployed Worker failures, regressions, and missing operational signals using Cloudflare Issues, logs, traces, SQL, or Observability MCP. Produce bounded evidence and verify recurrence against the deployed version.
add-a-lib
Scaffold a new shared library under libs/ in the builders-stack monorepo. Use when code is needed in two or more places (apps or services) and should become a single source of truth consumed by package name. Covers the package.json, tsconfig, the one-public-door src/index.ts barrel, and wiring it into a consumer…
implement
Implement an agreed issue or spec through implementation, review, fixes, and a PR ready to merge.