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-spotlight-publishergit 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-spotlight-publisher)<a href="https://agentmods.dev/skills/dailyaiagents-cpu/dailyai-os/skill-spotlight-publisher"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/skill-spotlight-publisher/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-spotlight-publisher"><img src="https://agentmods.dev/badge/skills/dailyaiagents-cpu/dailyai-os/skill-spotlight-publisher.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.00139 | $0.00897 |
| Opus 5 | $0.00069 | $0.00449 |
| Sonnet 5 | $0.00028 | $0.00179 |
| Haiku 4.5 | $0.00014 | $0.00090 |
Grade A, and why
skill-spotlight-publisher 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skill-spotlight-publisher
The thesis: 340 skills is an inventory; one well-explained skill per day is a story. Daily skill-of-the-day spotlights turn the catalog into a year-long content stream — 365 explainers per year, each one a Cooper-voice artifact a solo founder can read in 60 seconds and decide whether to use.
Procedure
bash skills/skill-spotlight-publisher/run.sh # daily run
bash skills/skill-spotlight-publisher/run.sh --skill <name> # spotlight a specific skill
bash skills/skill-spotlight-publisher/run.sh --dry-run # pick + render, no publish
Pipeline
- Pick a skill from
skills/<X>/SKILL.mdweighted by: a. Has not been spotlit in last 60 days (stored atdata/skill-spotlights/_history.json). +5 weight. b. SKILL.md is non-trivial (>50 lines). +2 weight. c. owner_agent is set (P5 compliant). +1 weight. d. NOT a stretch-skill (heuristic: name doesn't start with_). +1 weight. - Read the chosen skill's SOUL.md + SKILL.md (full).
- Local Ollama call (qwen3.5:latest, think=false, ~600 num_predict):
- System prompt: VOICE.md sentence rules + spotlight framing.
- Asks for a 200-word explainer for a solo founder unfamiliar with DAI OS. Three-part shape: what it solves / when to reach for it / the single most surprising thing about it.
- Voice-gate (newsletter surface, threshold 70 HARD).
- Scrubber HARD on the explainer.
- Both pass → write to
site/skills/<slug>/spotlight.html, append tosite/skills/index.html(or create), append to_history.json. Either fails → write todata/skill-spotlights/drafts/<YYYY-MM-DD>-<slug>.md.
Status codes
STATUS=ok skill=<slug> path=<html> (published)
STATUS=draft skill=<slug> path=<md> reason=<voice|scrubber> (held for review)
STATUS=skip reason=ollama-down|no-eligible-skill
STATUS=error reason=<...>
Output schema (site/skills//spotlight.html)
Static-template HTML wrapping a 200-word explainer with:
- Skill name (h1)
- Owner agent (subtitle)
- Three-section explainer body
- Footer link back to /skills/ and back to / and to GitHub source if public
What ships with it
3 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 · 79 lines · 139 tokens per session scan A 4d2461bbe39a
skill-spotlight-publisher is a skill published in the GitHub repository dailyaiagents-cpu/dailyai-os (0 stars, last pushed 4mo ago), licensed MIT. It adds 139 tokens to every session and 897 once invoked, about $0.0007 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…