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/kint4/autoframe/coverage-mapnpx skills add kint4/autoframe --skill coverage-mapgit clone --depth 1 https://github.com/kint4/autoframeWhat 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.00035 | $0.00388 |
| Opus 5 | $0.00017 | $0.00194 |
| Sonnet 5 | $0.00007 | $0.00078 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
coverage-map 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.
What it actually says
/coverage-map — Map Test Coverage
Type: Functional Description: Reads all spec files and maps them against requirements or features, showing what is covered, what is missing, and what is redundant.
Input Format
Optional:
- A list of requirements / features (pasted or via connector)
- A feature name to scope the report
With no input, map all existing E2E specs by feature folder.
Output Format
A coverage table grouped by feature:
| Feature | Covered | Missing | Redundant |
|---|
Plus a short prose summary and a prioritized list of gaps to close (with the suggested skill for each).
Step-by-Step Instructions
- Enumerate every spec under
tests/e2e/(and the feature folders). - Parse each spec's
test.describeandtestnames to build the list of covered behaviors. - If requirements were provided, align covered behaviors to each requirement; otherwise infer expected coverage from the feature and existing Page Objects.
- Identify:
- Covered — requirement has at least one passing-shaped test.
- Missing — requirement with no matching test.
- Redundant — multiple tests asserting the same behavior with no added value.
- Render the coverage table grouped by feature.
- Give a prioritized gap list, recommending
/tc-to-specor/new-specto close each gap. - For stakeholder-facing summaries, point to
/report.
Rules
- Read specs, never execute them, to build the map.
- Be explicit about assumptions when requirements are not provided.
- Group everything by feature to match the folder structure.
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 · 48 lines · 35 tokens per session scan A 15267a88a1d0
coverage-map is a skill published in the GitHub repository kint4/autoframe (6 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 388 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-31.
Other skills, from other repositories
tokenless
Use when a task can be delegated through the globally installed Tokenless CLI without directly writing to the workspace; route it to a visible AI provider website to save agent tokens.
tokenless-install
Install, upgrade, repair, and verify Tokenless, its agent skills, and local Playwright runtime. Use only when the user explicitly asks for installation, upgrade, repair, browser sign-in handoff, a failed doctor check, or an installation integrity check.
agent-qa-authoring
Use when creating, editing, validating, or running agent-qa tests, suites, or hooks. Prefer agent-qa MCP tools, enforce canonical agent-qa IDs, and use the bundled schema reference to avoid hallucinated config keys or YAML fields.
agent-qa-debug-fix
Use after an agent-qa run has failed and you need to debug, patch, and verify the issue using MCP evidence, logs, artifacts, and local code changes instead of generated fix suggestions.
linggan-talking-cards
将中文或英文口播文案与可选截图拆成 3–10 张 PPT 式演示卡片，输出文字准确的 PNG 卡片、结构化 manifest 和带逐卡口播台词的响应式 HTML 预览页。支持 3:4、16:9、9:16、4:3 四种比例，以及苹果白色毛玻璃、糖果、Obsidian、新丑风等 10 种视觉系统；适用于“口播文案拆解PPT生多图”“把逐字稿做成卡片”“给口播配 slides”“截图放进讲解卡片”“生成多图和预览页”“换一种 PPT 风格”以及修改指定卡片的请求。.
k6-load-testing
Comprehensive k6 load testing skill for API, browser, and scalability testing. Write realistic load scenarios, analyze results, and integrate with CI/CD.