Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/getkyo/kyonpx agentmods add skills/getkyo/kyo/readme-verifyWrote 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/getkyo/kyo/readme-verify)<a href="https://agentmods.dev/skills/getkyo/kyo/readme-verify"><img src="https://agentmods.dev/badge/skills/getkyo/kyo/readme-verify/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/getkyo/kyo/readme-verify"><img src="https://agentmods.dev/badge/skills/getkyo/kyo/readme-verify.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.00000 | $0.03796 |
| Opus 5.5 | $0.00000 | $0.01518 |
| Sonnet 5.5 | $0.00000 | $0.00759 |
| Haiku 4.5 | $0.00000 | $0.00380 |
Grade A, and why
readme-verify 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 20d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
readme-verify
Final gate. The README is either a fresh draft from readme-draft or the post-edit output from readme-edit. This skill does not modify the README; it verifies and reports.
Five gates run in this order. If a gate fails, report the failure and stop. Downstream gates run only when upstream gates pass cleanly.
Gate 4 (source-coverage) and Gate 5 (catalog detection) are the load-bearing gates. Gates 1-3 check self-consistency, skim experience, and structural shape; they pass even when the README is missing entire chapters of public surface (Gate 4 catches that) or reads as a catalog rather than teaching (Gate 5 catches that). Gate 5 is the mechanical sibling of readme-critique: it surfaces signals; the critique skill makes the gestalt judgment.
Gate 0: sbt doctest (MANDATORY, hard gate, runs first)
This gate is non-negotiable. EVERY fenced ```scala block in the README must compile via the project's sbt-kyo-doctest plugin. The script-level checks below are NOT a substitute. A README that the structural-script declares clean can still contain fabricated API names, hallucinated type syntax, dead val placeholders, or .copy calls on private[kyo] constructors. Only the compiler catches those.
Run:
sbt '<module-sbt-name>/doctest' 2>&1 | tee /tmp/doctest-verify.log
For kyo-data that is sbt 'kyo-dataJVM/doctest'. For kyo-http that is sbt 'kyo-httpJVM/doctest'. Use the project name git grep -nE "^lazy val ..kyo-<name>." build.sbt resolves to ; do not invent the sbt module name.
Parse the summary line that names the README under verification:
[info] doctest: <module>/README.md: total=N compiled=N cacheHits=N warnings=N failures=N
Pass conditions (ALL must hold):
- sbt exit code == 0.
failures=0in the summary.- The string
doctest: validation faileddoes NOT appear anywhere in the log.
Fail conditions (ANY triggers BLOCK):
- sbt exit code != 0.
failures=value > 0.- The phrase
doctest: validation failedappears. - Doctest reports "skipped: not wired to kyo-doctest" AND the module SHOULD be wired (kyo-* modules under the kyo monorepo are wired by default unless explicitly disabled via
.disablePlugins(KyoDoctestPlugin); if the verify agent encounters "skipped" for such a module, that is a build-config bug, not a pass).
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.
- 20d ago Changed 7e3de471ea35
- 1mo ago First seen · 216 lines · 0 tokens per session scan A 3f8e65f502bb
readme-verify is a skill published in the GitHub repository getkyo/kyo (822 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,796 tokens. 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.