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 dailyaiagents-cpu/dailyai-os --skill skill-coverage-monitorgit clone --depth 1 https://github.com/dailyaiagents-cpu/dailyai-osWrote 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/dailyaiagents-cpu/dailyai-os/skill-coverage-monitor)<a href="https://agentmods.dev/skills/dailyaiagents-cpu/dailyai-os/skill-coverage-monitor"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/skill-coverage-monitor/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/dailyaiagents-cpu/dailyai-os/skill-coverage-monitor"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/skill-coverage-monitor.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.00069 | $0.01000 |
| Opus 5 | $0.00034 | $0.00500 |
| Sonnet 5 | $0.00014 | $0.00200 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
skill-coverage-monitor 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 12d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-coverage-monitor
Why this exists
We have 110 skills in the repo and 344 in ~/.openclaw/skills/. Coverage is uneven — some skills are missing SOUL.md, others have a SKILL.md but no run.sh, others have neither a plist nor a "called-on-demand" marker (so it's unclear how they fire). This skill walks the registry and reports missing pieces so we can fix them or retire dead skills.
How to run
bash skills/skill-coverage-monitor/run.sh # report repo + ~/.openclaw skills
bash skills/skill-coverage-monitor/run.sh --root PATH # report only PATH
bash skills/skill-coverage-monitor/run.sh --json # JSON output
bash skills/skill-coverage-monitor/run.sh --report PATH # write markdown report to PATH
bash skills/skill-coverage-monitor/run.sh --voice-min N # voice score floor (default 75)
bash skills/skill-coverage-monitor/run.sh --skill SKILL_NAME # report only one skill
Validation per skill
For each skills/<name>/ dir, check 4 fields:
| Field | Pass condition | Severity if missing |
|---|---|---|
SOUL.md |
File exists; voice/score.py returns score ≥ --voice-min (default 75) |
YELLOW (<75) or RED (file missing) |
SKILL.md |
File exists; has YAML frontmatter with name: and description: |
RED if missing or unreadable frontmatter |
run.sh |
File exists; -x (executable). |
YELLOW (not executable) or RED (file missing) |
| Trigger | Either: a *.plist references the skill OR SKILL.md declares on-call: true (callable from another skill) |
YELLOW if both missing |
Trigger detection sources:
~/Library/LaunchAgents/*.plist— searchProgramArgumentsstrings forskills/<name>/run.shconfig/launchd/*.plist(recursive, exclude_archive/)openclaw cron list— match skill name in cron description column- SKILL.md frontmatter:
scheduled:,trigger:,on-call:
Output
Human-friendly:
[skill-coverage-monitor] 110 skills walked
fully-covered: 65
missing-trigger: 18 (no plist, no cron, no on-call)
missing-run.sh: 4
missing-SOUL.md: 3
voice-below-min: 2 (SOUL.md exists but score <75)
duplicates-in-~: 8 (same name in repo and ~/.openclaw/skills)
reports written to: data/skill-coverage/2026-05-07.md
What ships with it
2 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.
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.
- 12d ago First seen · 74 lines · 69 tokens per session scan A b0e7382b9dfd
skill-coverage-monitor is a skill published in the GitHub repository dailyaiagents-cpu/dailyai-os (0 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 1,000 once invoked, about $0.0003 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
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…
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…