Borrowing it
Nothing to install: this file belongs to shanraisshan/claude-code-hooks. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/shanraisshan/claude-code-hooks/main/.claude/commands/workflows/workflow-changelog.mdgit clone --depth 1 https://github.com/shanraisshan/claude-code-hooksWrote 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/commands/shanraisshan/claude-code-hooks/workflow-changelog)<a href="https://agentmods.dev/commands/shanraisshan/claude-code-hooks/workflow-changelog"><img src="https://agentmods.dev/badge/commands/shanraisshan/claude-code-hooks/workflow-changelog.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.1 | $0.00013 | $0.03407 |
| Opus 5 | $0.00006 | $0.01703 |
| Sonnet 5 | $0.00003 | $0.00681 |
| Haiku 4.5 | $0.00001 | $0.00341 |
Grade A, and why
workflow-changelog 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 8d 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Changelog
You are a coordinator for the claude-code-hooks project. Your job is to launch two research agents in parallel, wait for their results, merge findings, and present a unified report.
Versions to check: $ARGUMENTS (default: 10 if empty or not a number)
This is a read-then-report workflow. Launch agents, merge results, and produce a report. Only take action if the user approves.
Phase 0: Launch Both Agents in Parallel
Immediately spawn both agents using the Task tool in the same message (parallel launch):
Agent 1: workflow-changelog-agent
Spawn using subagent_type: "workflow-changelog-agent". Give it this prompt:
Research the claude-code-hooks project for changelog drift. Check the last $ARGUMENTS versions (default: 10).
Fetch these 3 external sources:
- Hooks Reference: https://code.claude.com/docs/en/hooks
- Hooks Guide: https://code.claude.com/docs/en/hooks-guide
- Changelog: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md
Then read all local repository files (settings, hooks.py, config, README, HOOKS-README, install settings, presentation) and analyze differences. Return a structured findings report covering missing hooks, configuration drift, version mismatches, hook behavior changes, bug fixes, matcher accuracy, presentation staleness, agent frontmatter hooks, and schema hook discovery (hidden hooks in settings.json schema propertyNames enum not in docs).
Agent 2: claude-code-guide
Spawn using subagent_type: "claude-code-guide". Give it this prompt:
Research the latest Claude Code hooks system. I need you to find:
- The complete list of all currently supported hook events (e.g. PreToolUse, PostToolUse, Stop, etc.) with their descriptions
- Any new hooks or hook changes introduced in recent Claude Code versions
- New hook input fields, matcher values, or configuration options added recently
- Any new hook types (command, prompt, agent) or new environment variables
- Changes to agent/skill frontmatter hook support
- Any bug fixes related to hooks
- New features in Claude Code that relate to hooks (e.g. new tool names for matchers, new subagent types)
Be thorough — search the web, fetch docs, and provide concrete version numbers and details for everything you find.
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.
- 8d ago First seen · 236 lines · 13 tokens per session scan A 5afc4d15036c
workflow-changelog is a command published in the GitHub repository shanraisshan/claude-code-hooks (539 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 3,407 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
swarm-init
Initialize a Claude Flow swarm with specified topology and configuration.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.
run-loop
Chain-aware loop driver. Works through implementation-plan tasks unattended — branch, build, ship a draft PR, dispatch the verifier, checkpoint, repeat — until the target is reached, the circuit breaker trips, or the task budget is spent. Never merges.