Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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-analyze-source)<a href="https://agentmods.dev/skills/getkyo/kyo/readme-analyze-source"><img src="https://agentmods.dev/badge/skills/getkyo/kyo/readme-analyze-source.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.1 | $0.00040 | $0.04773 |
| Opus 5 | $0.00020 | $0.02387 |
| Sonnet 5 | $0.00008 | $0.00955 |
| Haiku 4.5 | $0.00004 | $0.00477 |
Grade A, and why
readme-analyze-source 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 6d 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
readme-analyze-source
Read the module source directory given in $ARGUMENTS and produce three artifacts: a spine candidate, a list of callout candidates, and an API surface inventory. These artifacts are consumed by readme-draft and readme-analyze-existing. This skill does NOT draft a README, evaluate any existing README, or verify output.
What you produce
## Spine candidate
[use-case-first|type-first]
<spine paragraph here>
## Callout candidates
- <source file>:<line> -- <one-line summary>
- <file-A>:<line-A> + <file-B>:<line-B> -- <cross-API seam summary>
- ...
## API surface inventory
- <load-bearing type/method>: <one-line description of role>
- ...
## Section clusters
- "<Cluster name (use, not API)>" -- <one-sentence mental model>
- <API in this cluster>: <one-line role>
- ...
- ...
## Running-domain seeds
- <case class declarations + which clusters they can demonstrate>
- ...
Output these five sections and nothing else. The downstream skills consume this structure directly.
Input
A path to a module source directory (for example, kyo-http/).
This sub-skill MUST NOT read the existing README at the module path even if one exists. The spine candidate produced here is the 0(a)(i) source-only draft that downstream cleanup discipline depends on. Reading the existing README would anchor the spine on its wording and defeat the technique.
Step 1: read the source
Scan these locations in order:
- The package object's scaladoc (top of
package.scalaorpackage objectin the primary source tree). - Top-level scaladocs on the main public types and the primary entry-point companions.
- Method-level scaladocs on load-bearing methods (especially those with qualifiers:
Unsafe,Lazy,Default,Async). - Test case names under
src/test: names shaped "fails when...", "returns empty when...", "throws when..." describe edge behavior. - Implementation comments shaped "// This looks wrong but..." or "// Note:" in source.
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.
- 6d ago First seen · 347 lines · 40 tokens per session scan A f77f0a7bab67
readme-analyze-source is a skill published in the GitHub repository getkyo/kyo (812 stars, last pushed today), licensed Apache-2.0. It adds 40 tokens to every session and 4,773 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…