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.
git clone --depth 1 https://github.com/kellykampen/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/commands/kellykampen/agent-skills/add-to-changelog)<a href="https://agentmods.dev/commands/kellykampen/agent-skills/add-to-changelog"><img src="https://agentmods.dev/badge/commands/kellykampen/agent-skills/add-to-changelog/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/commands/kellykampen/agent-skills/add-to-changelog"><img src="https://agentmods.dev/badge/commands/kellykampen/agent-skills/add-to-changelog.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.00014 | $0.00684 |
| Opus 5 | $0.00007 | $0.00342 |
| Sonnet 5 | $0.00003 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
add-to-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 11d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add to Changelog Command
Add a new entry to the project's CHANGELOG.md file following the Keep a Changelog format and Semantic Versioning standards.
What this command does
- Parses arguments - Extracts version, change type, and message from command arguments
- Manages CHANGELOG.md - Creates the file if it doesn't exist with proper header structure
- Organizes entries - Adds entries to appropriate version sections and change type categories
- Maintains format - Ensures consistent formatting according to Keep a Changelog standards
- Version management - Creates new version sections with timestamps when needed
Command Execution
The command will:
- Parse the provided arguments: version, change type, and message
- Check if CHANGELOG.md exists in the project root
- If the file doesn't exist, create one with standard Keep a Changelog header
- Look for an existing section for the specified version
- If version section exists, add the entry under the appropriate change type
- If version section doesn't exist, create new version section with today's date
- Format the entry according to Keep a Changelog conventions
- Write the updated content back to the file
Usage
/add-to-changelog <version> <change_type> <message>
Parameters
<version>- Version number following semantic versioning (e.g., "1.1.0", "2.0.0-beta.1")<change_type>- One of: "added", "changed", "deprecated", "removed", "fixed", "security"<message>- Description of the change (use quotes for multi-word descriptions)
Examples
/add-to-changelog 1.1.0 added "New waitlist referral source configuration"
/add-to-changelog 1.0.2 fixed "Bug in subscription billing proration logic"
/add-to-changelog 2.0.0 changed "Migrated to new authentication system"
/add-to-changelog 1.2.1 security "Updated dependencies to address vulnerabilities"
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.
- 11d ago First seen · 94 lines · 14 tokens per session scan A cfaf4cfcf05d
add-to-changelog is a command published in the GitHub repository kellykampen/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 684 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-31.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.