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 YangsonHung/awesome-agent-skills --skill git-weekly-report-cngit clone --depth 1 https://github.com/YangsonHung/awesome-agent-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/yangsonhung/awesome-agent-skills/git-weekly-report-cn)<a href="https://agentmods.dev/skills/yangsonhung/awesome-agent-skills/git-weekly-report-cn"><img src="https://agentmods.dev/badge/skills/yangsonhung/awesome-agent-skills/git-weekly-report-cn/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/yangsonhung/awesome-agent-skills/git-weekly-report-cn"><img src="https://agentmods.dev/badge/skills/yangsonhung/awesome-agent-skills/git-weekly-report-cn.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.00029 | $0.01017 |
| Opus 5 | $0.00015 | $0.00508 |
| Sonnet 5 | $0.00006 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
git-weekly-report-cn 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 10d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git 周/日报生成
Overview
提取 Git 提交日志并生成结构化日报或周报。输出会把近期工作整理为完成事项、进行中事项、重要事项、计划和风险阻塞，并支持按时间范围、作者和仓库维度汇总，便于复用到站会、日报、周报或项目汇总中。
何时使用
当用户有以下需求时使用本技能：
- 从 Git 提交记录生成周报或日报
- 总结昨天或今天的 Git 活动
- 汇总一个或多个仓库的近期 Git 活动
- 回顾某个时间段内完成的工作
- 将提交历史整理为分类报告
- 从提交记录准备每日站会汇总
不要使用
以下场景不应使用本技能：
- 对特定变更的代码审查（请使用 code-reviewer）
- 查看单条提交的详细信息
- 提取日志以外的 Git 操作（分支、合并等）
- 与 Git 无关的报告生成
使用说明
- 确定日期范围和报告类型：
- 日报：用户说"昨天"、"今天"、"日报"时 — 默认
--since为昨天，--until为今天 - 周报：用户说"这周"、"本周"、"周报"时 — 默认
--since为本周一，--until为今天 - 其他情况：默认最近 7 天。接受用户自定义。
- 日报：用户说"昨天"、"今天"、"日报"时 — 默认
- 确定作者过滤。如用户指定则使用，默认：全部作者。
- 确定仓库路径。默认：当前工作目录。如用户提及多个项目，收集所有路径。
- 运行脚本：
python3 scripts/git_weekly_report.py --since <YYYY-MM-DD> --until <YYYY-MM-DD> [--author <名称>] [--repo <路径1> <路径2> ...]
- 读取 JSON 输出。脚本按仓库分组提供结构化提交数据。
- 使用 weekly-report-format.md 作为分类指南，按类型归类提交。
- 使用 weekly-report-template.md 作为输出结构生成最终周报。
- "下周计划"和"风险阻塞"板块：需向用户确认是否有内容补充，这些信息无法从 Git 日志推导。日报默认不含这些板块，除非用户要求。
- 呈现最终 Markdown 周报。如用户需要，保存到文件。
脚本使用
# 默认：最近 7 天，当前目录
python3 scripts/git_weekly_report.py
# 指定日期范围
python3 scripts/git_weekly_report.py --since 2026-04-21 --until 2026-04-28
# 指定作者
python3 scripts/git_weekly_report.py --since 2026-04-21 --author "Yang"
# 多个仓库
python3 scripts/git_weekly_report.py --since 2026-04-21 --repo /path/to/project-a /path/to/project-b
# 保存输出到文件
python3 scripts/git_weekly_report.py --since 2026-04-21 --output /tmp/weekly.json
# 包含 merge 提交
python3 scripts/git_weekly_report.py --since 2026-04-21 --merges
JSON 输出结构
脚本输出 JSON，结构如下：
date_range:{ since, until }— 查询的日期范围author_filter: 字符串或 null — 应用的作者过滤repositories:{ path, name, commit_count, commits }数组total_commits: 所有仓库的提交总数
每条提交包含：hash、short_hash、author、date、subject、body、refs。
周报生成
当单个仓库的提交数超过 50 条时，按类别汇总而非逐条列出。始终保留 short_hash 以便追溯。
"进行中的工作"板块，留意以下信号：WIP、TODO、临时方案、未合并的功能分支。
"重要事项"板块，识别：breaking change、安全修复、重大功能上线、涉及关键路径的提交。
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.
- 10d ago First seen · 90 lines · 29 tokens per session scan A b7dad000dc45
git-weekly-report-cn is a skill published in the GitHub repository YangsonHung/awesome-agent-skills (18 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 1,017 once invoked, about $0.0001 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
app-release
Automates the release process for Skill Lake app, including version bumping, building, packaging, and publishing to GitHub and Homebrew.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
history-portability
Import Claude Code or Codex history and move complete CCAM datasets between machines. Use when rescanning provider history, importing a copied directory, uploading JSONL or archives, exporting a backup, restoring it idempotently, or verifying that tokens, workflows, runs, rules, and pricing survived.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
reply-to-pr-threads
Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages".