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 YiShu5/claude-skills --skill skillgit clone --depth 1 https://github.com/YiShu5/claude-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/yishu5/claude-skills/skill)<a href="https://agentmods.dev/skills/yishu5/claude-skills/skill"><img src="https://agentmods.dev/badge/skills/yishu5/claude-skills/skill/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/yishu5/claude-skills/skill"><img src="https://agentmods.dev/badge/skills/yishu5/claude-skills/skill.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.00168 | $0.01152 |
| Opus 5.5 | $0.00067 | $0.00461 |
| Sonnet 5.5 | $0.00034 | $0.00230 |
| Haiku 4.5 | $0.00017 | $0.00115 |
Grade A, and why
会记成报 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
会记成报
把会议转写稿或会议笔记整理成可核对的会议纪要 + 我的日报 + 周报素材卡，并在用户提供本周多份已确认日报时合并去重生成周报。你的任务不是泛泛总结，而是只根据明确事实产出，确保负责人、完成状态和截止时间不被猜测。
输入
用户可能提供（任意组合）：
- 会议转写稿、会议笔记或聊天记录；
- 用户姓名或在会议中的称呼；
- 会议日期；
- 用户对事项状态、负责人、截止时间的补充；
- 多份已经由用户确认的日报或素材卡。
工作流程
第一步：识别会议信息
- 提取会议主题、日期、参会人、背景、明确结论、待办事项、负责人、截止时间和风险。
- 区分"讨论过""提出建议""已经决定"三种程度，不得把建议写成最终结论。
- 如果同一事项前后有变化，以最后一次明确决定为准，并在必要时说明发生了变更。
- 发现转写错误、角色不明或前后矛盾时，明确标记出来，不静默修正。
第二步：事实核对
- 检查负责人、截止时间、完成状态、关键数字是否明确。
- 缺少关键信息时，一次只问用户一个最影响结果的问题，不要一次抛出多个问题。
- 用户没有确认的信息一律写"待确认"，不得自行补全。
- 如果会议中没有待办，明确写"本次会议未识别到明确待办"，不得为了结构完整而编造。
第三步：生成会议纪要
严格使用以下结构，不增删栏目：
会议主题：
会议日期：
参会人：
一、会议结论
1、
二、待办事项
1、事项：
负责人：
截止时间：
验收结果：
三、待确认问题
1、
第四步：生成"我的日报"
- 只提取与用户本人有关、且在输入中有依据的内容。
- "✅"只用于输入中明确已经完成并有结果的事项。
- 未完成、进行中或状态不清的事项统一使用"🚶"。
- 不得把明日计划写成今日已完成。
- 严格使用以下格式，不增加栏目：
X月X日工作总结
✅：
1、
🚶：
1、
明日计划：
1、
- 没有内容的状态区保留栏目并写"无"。
第五步：生成周报素材卡
每场会议或每天输出一张素材卡：
- 日期：
- 事项：
- 本周新增进展：
- 当前状态：已完成/进行中/待确认
- 结果或证据：
- 下一步：
- 来源：会议主题或日报日期
第六步：合并周报
仅当用户提供本周多张已确认素材卡或日报时执行：
- 按事项合并，不按日期机械拼接。
- 同一事项只保留本周新增进展，不重复累计相同描述。
- 保留明确结果、数据和当前最终状态。
- 未确认日报不得当作已完成事实。
- 严格使用以下结构：
本周工作进展
1、
下周计划
1、
发布边界
- 所有输出都必须先让用户核对。
- 未收到"确认"前，只能生成草稿，不得代替用户发送到群、文档或其他渠道。
- 提醒文字必须放在可复制正文之外，原文为： "请逐条核对事项、负责人、完成状态、数据和计划，确认无误后再发送。"
表达要求
- 简洁、具体，保留业务名词和关键数字。
- 不夸大、不编造、不改变原意。
- 用户纠正事实（如负责人、状态、时间）后，基于新事实重新生成，并说明修改了哪一项。
示例
参见 examples.md，了解一次完整运行的输入、追问、V1/V2 纠错与周报合并示例。
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 · 122 lines · 168 tokens per session scan A bfac436d9d7b
会记成报 is a skill published in the GitHub repository YiShu5/claude-skills (132 stars, last pushed yesterday), licensed MIT. It adds 168 tokens to every session and 1,152 once invoked, about $0.0007 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-12.
Other skills, from other repositories
agentflow
Orchestrate autonomous AI development pipelines through your Kanban board (Asana, GitHub Projects, Linear). Manages multi-worker Claude Code dispatch, deterministic quality gates, adversarial review, per-task cost tracking, and recoverable pipeline design.
asana-automation
Automate Asana tasks via Rube MCP (Composio): tasks, projects, sections, teams, workspaces. Always search tools first for current schemas.
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
retro
Facilitate a structured sprint retrospective — what went well, what didn't, and prioritized action items with owners and deadlines. Use when running a retrospective, reflecting on a sprint, creating action items from team feedback, or learning how to run effective retros.
sprint-plan
Plan a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, selecting stories, or balancing sprint scope against velocity.
stakeholder-map
Build a stakeholder map using a power/interest grid, identify communication strategies per quadrant, and generate a communication plan. Use when managing stakeholders, preparing for a launch, aligning cross-functional teams, or planning stakeholder engagement.