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 zocomputer/skills --skill zo-daily-news-digestgit clone --depth 1 https://github.com/zocomputer/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/zocomputer/skills/zo-daily-news-digest)<a href="https://agentmods.dev/skills/zocomputer/skills/zo-daily-news-digest"><img src="https://agentmods.dev/badge/skills/zocomputer/skills/zo-daily-news-digest/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/zocomputer/skills/zo-daily-news-digest"><img src="https://agentmods.dev/badge/skills/zocomputer/skills/zo-daily-news-digest.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.00023 | $0.00419 |
| Opus 5.5 | $0.00009 | $0.00168 |
| Sonnet 5.5 | $0.00005 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
daily-news-digest 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 1mo 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
Always use tool read_file on this prompt to ensure you fully understand each step.
Help User Set Up a Daily News Digest
What to do
You are helping the user create an automation that fetches news and emails it to them. Your goal is to configure the agent to find the right content and deliver it on schedule.
Step 1: Clarify the details
You already know they want a daily news digest. Ask about:
- Topic: What specific topics or keywords are they interested in?
- Schedule: What time in the morning should it be sent? (and timezone if needed)
- Delivery: Confirm the email address to send to.
- Sources: Do they have preferred news sources or should it be general?
Step 2: Set Up the Automation
Once you have the details:
- Check prerequisites: Ensure they have a way to send email (e.g., Gmail integration) if the agent needs to send it as them, or clarify how the agent will send it.
- Create the agent: Use
tool create_scheduled_taskwith a clear instruction.- Example instruction: "Every day at 8am, search for the latest news about [Topic], summarize the top 5 headlines with links, and send an email to [User's Email] with the summary."
- Finally: Tell them:
You can test, edit, or delete this automation by opening the Agents tab from the left rail (or top-right menu on mobile).
Key Tips
- Be specific: The more specific the topic, the better the results.
- Start simple: Ensure the basic flow (search -> summarize -> email) works before adding complex filtering.
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.
- 1mo ago First seen · 44 lines · 23 tokens per session scan A a7b314a67493
daily-news-digest is a skill published in the GitHub repository zocomputer/skills (46 stars, last pushed 2mo ago), licensed MIT. It adds 23 tokens to every session and 419 once invoked, about $0.0001 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-09-03.
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…