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 agentmods add skills/rockyflux/yq-workflow/commit-daily-summarynpx skills add rockyflux/yq-workflow --skill commit-daily-summarygit clone --depth 1 https://github.com/rockyflux/yq-workflowWrote 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/rockyflux/yq-workflow/commit-daily-summary)<a href="https://agentmods.dev/skills/rockyflux/yq-workflow/commit-daily-summary"><img src="https://agentmods.dev/badge/skills/rockyflux/yq-workflow/commit-daily-summary.svg" alt="Measured on agentmods" 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 | $0.00056 | $0.00820 |
| Opus 5 | $0.00028 | $0.00410 |
| Sonnet 5 | $0.00011 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
commit-daily-summary 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 5d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
commit-daily-summary
Overview
Use this skill to turn one day of git commits into a readable work summary. The goal is not to dump commit lines, but to translate them into grouped, human-friendly task statements.
Core Rules
- Default scope is today in the user's local timezone unless the user gives a date.
- Prefer git evidence over memory.
- Group commits by workstream / theme, not just by repository order.
- Rewrite raw commit messages into concise Chinese action summaries.
- Do not include empty, noise-only, or clearly meaningless commits as standalone achievements.
Workflow
Step 1: Determine the date and repo scope
Default assumptions:
- date range: today
- repository scope: current repository unless the user asks for multiple repositories
Clarify only when necessary:
- today vs a specific date
- current repo vs multiple repos
- whether the user wants only task summaries or task summaries + raw commit details
Step 2: Collect commits
Use direct git commands with explicit repository paths.
Recommended command pattern:
git -C <repo> log --since="YYYY-MM-DD 00:00" --until="YYYY-MM-DD 23:59:59" --pretty=format:"%h%x09%s"
If no commits are found, state that clearly.
Step 3: Group commits into workstreams
Cluster related commits together, for example:
- 同一功能开发
- 同一缺陷修复
- 同一配置或工具链调整
- 同一文档更新
Do not create one task sentence per commit if several commits are obviously part of the same workstream.
Step 4: Rewrite into Chinese action summaries
Good summary lines should:
- start with a clear action verb
- describe the actual business or engineering result
- omit noisy implementation trivia unless it matters
- be understandable to someone reading a daily report quickly
Examples:
- 实现了行情页的筛选条件持久化
- 修复了任务轮询在终态下未刷新概览的问题
- 重构了图表数据映射逻辑，降低了重复处理分支
- 补充了设置保存链路的回归测试
Step 5: Output the daily report
Preferred structure:
- 日期范围
- 今日工作摘要
- 仓库 / workstream 明细
- 如有需要，再附原始 commits
Recommended Output Shape
## 提交总结
- 日期：2026-03-30
- 范围：today / current repo
### 今日工作摘要
- ...
- ...
### 分项明细
#### 仓库 A
- workstream 1: ...
- workstream 2: ...
### 原始提交（可选）
- abc123 feat(...)
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.
- 5d ago First seen · 125 lines · 56 tokens per session scan A e5be8f536332
commit-daily-summary is a skill published in the GitHub repository rockyflux/yq-workflow (2 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 820 once invoked, about $0.0003 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-31.
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.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
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…