A command for checking whether recent software changes are documented in the relevant changelog. A changelog is the file that records user-visible changes between releases.

Use it before a release to review commits since the last version, match changes to affected packages, and verify changelog entries for pull requests.

It helps catch missing release notes before publishing a new version. It also checks package-specific entries and the required format for outside contributions.

cl — Command by code-yeongyu

Install

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.

agentmods

npx agentmods add commands/code-yeongyu/senpi/cl

Clone the repo

git clone --depth 1 https://github.com/code-yeongyu/senpi

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 580 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00006	$0.00580
Opus 5	$0.00003	$0.00290
Sonnet 5	$0.00001	$0.00116
Haiku 4.5	$0.00001	$0.00058

Measured yesterday against content hash 40bde8c5d091, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cl 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 yesterday.

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.

.github/agent/commands/cl.md · 58 lines

How it starts

The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Audit changelog entries for all commits since the last release.

Process

Find the last release tag:

git tag --sort=-version:refname | head -1

List all commits since that tag:
```
git log <tag>..HEAD --oneline
```
Read each package's [Unreleased] section:
- packages/ai/CHANGELOG.md
- packages/agent/CHANGELOG.md
- packages/tui/CHANGELOG.md
- packages/coding-agent/CHANGELOG.md
For each commit, check:
- Skip: changelog updates, doc-only changes, release housekeeping, upstream-sync merge commits themselves.
- Skip: changes to generated model catalogs (for example packages/ai/src/models.generated.ts, packages/ai/src/image-models.generated.ts) unless accompanied by an intentional product-facing change in non-generated source/docs.
- Determine which package(s) the commit affects (use git show <hash> --stat).
- Verify a changelog entry exists in the affected package(s).
- For external contributions (PRs), verify format: Description ([#N](url) by [@user](url)).
Cross-package duplication rule: Changes in ai, agent or tui that affect end users should be duplicated to the coding-agent changelog, since coding-agent is the user-facing package that depends on them.
Report:
- List commits with missing entries.
- List entries that need cross-package duplication.
- Add any missing entries directly under ## [Unreleased].

Changelog Format Reference

Sections (in order):

### Breaking Changes - API changes requiring migration
### Added - New features
### Changed - Changes to existing functionality
### Fixed - Bug fixes
### Removed - Removed features

Attribution:

Internal: Fixed foo ([#123](https://github.com/code-yeongyu/senpi/issues/123))
External: Added bar ([#456](https://github.com/code-yeongyu/senpi/pull/456) by [@user](https://github.com/user))

Rules

Before adding entries, read the full [Unreleased] section to see which subsections already exist.
New entries ALWAYS go under ## [Unreleased].
Append to existing subsections (e.g. ### Fixed); do not create duplicates.
NEVER modify already-released version sections. Each version section is immutable once released.

Read the full file on GitHub · 58 lines

Changes

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.

yesterday First seen · 58 lines · 6 tokens per session scan A 40bde8c5d091

Subscribe to this mod's changes

cl is a command published in the GitHub repository code-yeongyu/senpi (411 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 580 once invoked, about $0.0000 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.

Code review Data and AI Git and workflow LLM agent ai-agent cli coding-agent llm-tools

cl

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Process

Changelog Format Reference

Rules

What this file has done since we first saw it

Other commands, from other repositories

AGENTS

global-shortcuts

speckit.archive

speckit.extract.run

speckit.critique.run

speckit.iterate.apply