Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add chengkj99/kj-skills/plugin install kj-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/chengkj99/kj-skills/weekly-digest)<a href="https://agentmods.dev/skills/chengkj99/kj-skills/weekly-digest"><img src="https://agentmods.dev/badge/skills/chengkj99/kj-skills/weekly-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/chengkj99/kj-skills/weekly-digest"><img src="https://agentmods.dev/badge/skills/chengkj99/kj-skills/weekly-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.00150 | $0.02940 |
| Opus 5 | $0.00075 | $0.01470 |
| Sonnet 5 | $0.00030 | $0.00588 |
| Haiku 4.5 | $0.00015 | $0.00294 |
Grade A, and why
weekly-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 11d 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 — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Digest（Git 周报生成器）
从 Git 历史生成可核验的中文周报。先采集事实，再按受众重组表达；不得把 Git 无法证明的信息写成事实。
语言与事实边界
- 所有面向用户的输出使用中文；代码、路径、变量名保持原文。
- 提交数、代码行数、文件数、作者、项目名必须来自
scripts/collect.sh或等价的真实 Git 命令，且保留其统计范围。 - Git 只能证明代码活动，不能证明上线、完成度、业务结果、阻塞、风险、下周计划或客户承诺。缺少用户提供的佐证时，省略这些字段，或标为「待补充」，不得推断。
- 不向客户或高管视图暴露 commit hash、作者邮箱、内部路径、代码行数等实现细节，除非用户明确要求。
口令与视图
| 口令 | 作用 |
|---|---|
/weekly-digest、周报、本周总结 |
默认工程视图：本周 + 上周趋势 |
多项目周报、团队周报 |
聚合多个本地 Git 仓库 |
扫描目录生成周报、扫描 {目录} 的周报 |
扫描目录内的 Git 仓库，列出本周有提交的项目后等待选择 |
只看本周 |
仅输出本周，不做上周对比 |
给领导、管理者视图 |
面向直属领导：结果、风险/需支持、下周重点 |
团队同步、给团队 |
面向协作团队：模块进展、协作关注项 |
高管摘要、给高管 |
一页式 TL;DR、状态、关键产出、决策/风险 |
客户周报、给客户 |
对外里程碑式表达；仅写可由 Git 支撑的交付内容，其他信息标待确认 |
按人分类、按贡献者分类 |
以 Git author（姓名 + 邮箱）为一级分组 |
按人统计 |
默认主题视图后追加贡献者汇总表 |
关联 PR |
尝试关联 GitHub PR / Issue |
导出周报 |
写入 docs/weekly-digest/{week}.md |
周报 2026-05-19 |
指定该日期所在周 |
默认使用工程视图。用户同时指定多个受众时，先输出一个“事实底稿”，再分别渲染受众版本，避免不同版本的数据不一致。
执行流程
1. 确定范围与项目来源
- 用户明确列出仓库路径时，直接使用这些仓库；当前目录是 Git 仓库且未要求多项目时，直接使用当前仓库。
- 用户要求多项目、扫描目录，或当前目录不是 Git 仓库且未提供项目列表时，进入“扫描并选择”流程。不要擅自扫描用户主目录、工作区根目录或其他宽泛目录。
- 用户给出日期时，以该日所在周为本周；否则本周为本周一至今天，上周为上周一至上周日。
- 解析受众视图、贡献者视图、是否包含上周、PR 关联和导出要求。
2. 扫描并让用户选择项目
这是目录扫描模式的必经步骤，先发现活跃仓库、再征求选择、最后才采集周报详情。
-
确定扫描目录：优先使用用户明确给出的目录；否则读取
~/.claude/weekly-digest-projects.json中的scan_roots。两者都没有时，询问用户：“请提供要扫描的目录绝对路径，例如/Users/name/workspace。” -
扫描活跃仓库：运行以下命令，仅寻找本周当前分支有非 merge 提交的 Git 仓库：
./scripts/scan-repos.sh /path/to/workspace传入指定周的起始日：
./scripts/scan-repos.sh /path/to/workspace 2026-05-19默认只识别普通
.git目录，扫描时不向已识别的仓库内部继续递归；嵌套仓库需要用户显式提供其路径。扫描只读，不修改仓库。 -
展示候选清单：将脚本结果按提交数降序编号，给出项目名、路径、提交数和最新提交摘要。例如：
发现 3 个本周有变更的仓库： 1. loanfe-h5 — 8 次提交 — /work/loanfe-h5 最新：feat(order): add repayment entry 2. kj-skills — 3 次提交 — /work/kj-skills 最新：docs: refine weekly digest 3. admin-web — 1 次提交 — /work/admin-web 最新：fix: handle empty state 请选择要生成周报的项目：输入编号（如 `1,3` 或 `1-3`）、`全部`，或项目名；回复“取消”则结束。
What ships with it
8 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.
- 11d ago First seen · 158 lines · 150 tokens per session scan A 525aa42c77e7
weekly-digest is a skill published in the GitHub repository chengkj99/kj-skills (14 stars, last pushed 10d ago), licensed MIT. It adds 150 tokens to every session and 2,940 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-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage repo-sync on macOS for shared documents and team context. Use when asked what repo-sync does, to automatically sync a repo, add a repo to repo-sync, stop syncing or un-sync a repo, check sync health, configure repo-sync, uninstall it, or install and maintain its bundled agent skill. Ordinary one-time Git pulls…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.