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 ekline-io/ekline-docs-skills --skill docs-coveragegit clone --depth 1 https://github.com/ekline-io/ekline-docs-skillsWrote 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/ekline-io/ekline-docs-skills/docs-coverage)<a href="https://agentmods.dev/skills/ekline-io/ekline-docs-skills/docs-coverage"><img src="https://agentmods.dev/badge/skills/ekline-io/ekline-docs-skills/docs-coverage/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/ekline-io/ekline-docs-skills/docs-coverage"><img src="https://agentmods.dev/badge/skills/ekline-io/ekline-docs-skills/docs-coverage.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.00064 | $0.00778 |
| Opus 5.5 | $0.00026 | $0.00311 |
| Sonnet 5.5 | $0.00013 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
docs-coverage 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 2mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation coverage
Run the helper script to measure what percentage of your public API surface is documented.
Inputs
$ARGUMENTS— optional source directory and optional--docs-dir DIRfor the docs directory
Steps
1. Run the helper script
python scripts/scan_exports.py $ARGUMENTS
Pass --docs-dir DIR if the user specifies a docs directory. Capture the JSON output.
The script handles:
- Source file discovery (excludes test files, node_modules, vendor, dist, build)
- Export extraction: functions, classes, interfaces, types, const exports, components, API endpoints
- Inline doc detection: JSDoc for TS/JS, docstrings for Python, GoDoc for Go
- Doc file scanning to check if each export is mentioned in documentation
- Coverage calculation by type and directory
Supports TypeScript/JavaScript, Python, and Go. Max 300 source files per run.
2. Handle errors and empty results
If the JSON contains an error field:
not_a_directory— tell user the specified path is not a valid directory
If total_public_items is 0:
- Tell user no public API items were found, suggest checking the source directory path
Stop here if error or nothing found.
3. Present the coverage report
Show overall coverage from overall_coverage:
- Percentage, documented count, partial count, undocumented count, total
Show coverage by type from by_type:
- For each type (endpoint, class, function, component, type, interface), show percentage and counts
- Use a simple bar or fraction format
Show coverage by directory from by_directory:
- Top directories with their coverage percentages
4. Show undocumented items prioritized by type
List items from the undocumented array, grouped and prioritized:
- Endpoints — users depend on these directly
- Functions — high coupling, used by other modules
- Classes — core abstractions
- Types/interfaces — lower priority unless widely used
For each item show: name, file path, and line number.
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.
- 2mo ago First seen · 100 lines · 64 tokens per session scan A d9e70f9d97d2
docs-coverage is a skill published in the GitHub repository ekline-io/ekline-docs-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 778 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-08-31.
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…