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 commands/cloudai-x/claude-workflow-v2/summarize-changesgit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2What 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.00013 | $0.00426 |
| Opus 5 | $0.00006 | $0.00213 |
| Sonnet 5 | $0.00003 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
summarize-changes 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 3d 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
Context
- Current branch: !
git branch --show-current - Default branch: !
git remote show origin 2>/dev/null | grep 'HEAD branch' | cut -d' ' -f5 || echo "main" - Today's commits: !
git log --oneline --since="midnight" --author="$(git config user.email)" 2>/dev/null || echo "No commits today" - This week's commits: !
git log --oneline --since="1 week ago" --author="$(git config user.email)" 2>/dev/null | head -20 || echo "No commits this week" - Branch commits (vs main): !
git log --oneline $(git remote show origin 2>/dev/null | grep 'HEAD branch' | cut -d' ' -f5 || echo "main")..HEAD 2>/dev/null | head -20 || echo "No branch commits" - Files changed on branch: !
git diff --stat $(git merge-base HEAD origin/$(git remote show origin 2>/dev/null | grep 'HEAD branch' | cut -d' ' -f5 || echo "main"))..HEAD 2>/dev/null | tail -5 || echo "No changes"
Task
Generate a clear, concise summary based on the scope:
- today: What I did today (for standup)
- week: Weekly summary (for reports)
- branch: All changes on this branch (for PR)
- pr: Full PR description with sections
Format the output as:
- Summary: 1-2 sentence overview
- Changes: Bullet list of key changes
- Files: Main files affected
- Impact: What this enables or fixes
Scope: $ARGUMENTS
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.
- 3d ago First seen · 32 lines · 13 tokens per session scan A 50d87e1e1d69
summarize-changes is a command published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 8d ago), licensed MIT. It adds 13 tokens to every session and 426 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 commands, from other repositories
commit
Create a local git commit for source skills without pushing.
commit
Auto-stage, review, and commit all changes with a conventional commit message.
ship
Commit all changes and push to remote in one operation (combines /commit and /push).
commit
Create a well-crafted commit after running pro-workflow quality checks.
git-commit
Create a git commit for the current changes using Conventional Commits-style format.
commit-msg
Command "commit-msg" from doccker/cc-use-exp, covering 生成 git commit message, 执行步骤, 1. 获取变更内容, 查看已暂存的变更 and 如果没有暂存内容，查看所有变更.