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 MarsZ42/OrbitOS --skill ai-newslettersgit clone --depth 1 https://github.com/MarsZ42/OrbitOSWrote 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/marsz42/orbitos/ai-newsletters)<a href="https://agentmods.dev/skills/marsz42/orbitos/ai-newsletters"><img src="https://agentmods.dev/badge/skills/marsz42/orbitos/ai-newsletters/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/marsz42/orbitos/ai-newsletters"><img src="https://agentmods.dev/badge/skills/marsz42/orbitos/ai-newsletters.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.00035 | $0.00515 |
| Opus 5 | $0.00017 | $0.00258 |
| Sonnet 5 | $0.00007 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
ai-newsletters 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.
What it actually says
AI Newsletter Curation
Fetch, deduplicate, and rank AI newsletter content into a daily digest.
RSS Sources
- TLDR AI:
https://bullrich.dev/tldr-rss/ai.rss - The Rundown AI:
https://rss.beehiiv.com/feeds/2R3C6Bt5wj.xml
Workflow
-
Check cache: Look for
50_资源/Newsletters/YYYY-MM/YYYY-MM-DD-摘要.md. If exists with today's date, return cached content. -
Fetch feeds: Use WebFetch on both RSS URLs. Extract title, link, pubDate, description for each item.
-
Deduplicate: Merge items with similar titles (80%+ word overlap). Keep longer description, track both sources.
-
Rank items by:
- AI relevance (LLM, GPT, Claude, agents, ML keywords)
- Productivity relevance (workflow, automation, tools, PKM)
- Recency (newer = higher)
- Novelty (check recent archives, penalize repeats)
-
Generate digest: See TEMPLATE.md for format. Include:
- 精选推荐 (3-5 highest scoring) with content creation angles
- AI动态 section
- 生产力工具 section
- Stats footer
-
Save files:
50_资源/Newsletters/YYYY-MM/YYYY-MM-DD-摘要.md(curated)50_资源/Newsletters/YYYY-MM/原始数据/YYYY-MM-DD_TLDR-AI-Raw.md50_资源/Newsletters/YYYY-MM/原始数据/YYYY-MM-DD_Rundown-AI-Raw.md
Output Format
Manual invocation: Display full digest with all sections.
From /start-my-day: Return condensed list:
**内容机会 (5):**
- [标题] - [角度]
...
完整摘要: [[YYYY-MM-DD-摘要]]
Error Handling
- One feed down: Continue with other, note in digest
- Both down: Use yesterday's archive with warning
- Empty feeds: Create minimal digest noting "今日无新内容"
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.
- 12d ago First seen · 56 lines · 35 tokens per session scan A 2b689dd9898d
ai-newsletters is a skill published in the GitHub repository MarsZ42/OrbitOS (970 stars, last pushed 6mo ago), licensed MIT. It adds 35 tokens to every session and 515 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-30.
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…