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 leecyno1/boutique-skills --skill dasheng-daily-intakegit clone --depth 1 https://github.com/leecyno1/boutique-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/leecyno1/boutique-skills/dasheng-daily-intake)<a href="https://agentmods.dev/skills/leecyno1/boutique-skills/dasheng-daily-intake"><img src="https://agentmods.dev/badge/skills/leecyno1/boutique-skills/dasheng-daily-intake/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/leecyno1/boutique-skills/dasheng-daily-intake"><img src="https://agentmods.dev/badge/skills/leecyno1/boutique-skills/dasheng-daily-intake.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.00049 | $0.01012 |
| Opus 5 | $0.00024 | $0.00506 |
| Sonnet 5 | $0.00010 | $0.00202 |
| Haiku 4.5 | $0.00005 | $0.00101 |
Grade A, and why
dasheng-daily-intake 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 9d 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
dasheng-daily-intake(Final)
1) 定位
daily intake 是采集阶段唯一入口,只负责:
- 四渠道采集(
5173/18080/8001/web) - 底层数据库沉淀(JSON 本地落盘)
- 采集报告生成(热度筛选 + 重复归并 + 渠道汇总)
- 群交付(文档 + 截图 + JSON 路径)
边界固定:
intake = 收clustering = 并brief = 定
intake 不负责 clustering / brief 的执行。
2) 采集输入(硬约束)
时间窗口(统一约束)
- 所有渠道仅采集过去 24 小时内容。
- 条目不够时允许不足,禁止补旧内容凑量。
渠道规则
5173:xhs / douyin / bili / wb / x(仅 24h)18080:只采集微信公众号文章(仅 24h),不采集其他平台内容8001:微信公众号缓存(仅 24h)web:当天外部热点补充(仅 24h,若不足可为空)
3) 底层数据库(下游对接接口)
必须落地本地 JSON,并作为下一环节输入接口。
必交付文件
raw-topic-items.json(底层原子条目)intake-records.json(标准化条目)topic-merge-map.json(重复归并映射)intake-report.md(采集报告正文)
最小字段(raw-topic-items)
item_idsource_system(5173/18080/8001/web)source_platformsource_grouptitleorigin_urlpublish_timeheat_scorededupe_keycrawl_time
质量闸门
- 所有入选报告条目必须带原链接
- 所有渠道必须满足“24小时窗口”
- 下游接口默认读取
intake-records.json
4) 采集报告(必须可审)
报告按热度筛选并做重复归并,输出“主要题目池”。
必含结构
- 今日采集总览(总量、分渠道数量)
- 热度 Top 题目(跨渠道合并后)
- 重复归并结果(同题异源合并)
- 每个入选题目:
- 标题
- 来源链接(可多条)
- 入选原因(热度、时效、跨平台共振、可写性)
- 各渠道汇总小结:5173 / 18080 / 8001 / web
5) 群交付(编辑审核)
目标群:oc_975d43c5704bf8c755bb9e32bf7c3922
每次 intake 完成后必须发送以下内容:
- 采集报告(飞书文档链接)
5173截图:数据分析页切到context、search任务组热榜内容图18080截图:reports 页面生成图8001截图:微信公众号标签下文章列表图- 底层 JSON 路径回执:至少
raw-topic-items.json、intake-records.json
6) 发布前校验(未通过禁止报完成)
- 报告文档非空,且包含“主要题目 + 入选原因 + 链接”
- 三张截图齐全(5173 / 18080 / 8001)
- 底层 JSON 存在且可读
- 群消息必须包含 JSON 路径
- 报告明确标注“仅过去24小时;条目不足不补量”
一句话:
daily intake = 四渠道采集(统一24h) -> 底层JSON入库 -> 热度归并报告 -> 文档+截图+JSON路径发群审核。
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.
- 9d ago First seen · 112 lines · 49 tokens per session scan A a7ede4b25da0
dasheng-daily-intake is a skill published in the GitHub repository leecyno1/boutique-skills (5 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,012 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-09-03.
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…