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/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/changelog)<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/changelog"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/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/joaquimscosta/arkhe-claude-plugins/changelog"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/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.00018 | $0.00343 |
| Opus 5.5 | $0.00007 | $0.00137 |
| Sonnet 5.5 | $0.00004 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
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 today.
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
Changelog
Generate professional changelogs from git commit history with automatic categorization and semantic versioning.
Usage
/changelog [options]
Options
--since <commit/tag>- Generate since specific commit/tag (default: last tag)--until <commit/tag>- Generate until specific commit/tag (default: HEAD)--output <file>- Output file path (default: CHANGELOG.md)--format <style>- Output format: keepachangelog, conventional, github--version <version>- Version number (auto-detected if not provided)--append- Append to existing changelog--no-group- Don't group commits by type
Examples
/changelog # Generate since last tag
/changelog --since v1.0.0 --version 1.1.0 # Specific version range
/changelog --format github # GitHub-style format
Implementation
Invoke the Skill tool with skill name "git:generating-changelog" and arguments: $ARGUMENTS
The skill will handle git history analysis, commit categorization, semantic versioning detection, and multiple output formats.
For detailed documentation, see git/skills/generating-changelog/SKILL.md.
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.
- today First seen · 41 lines · 18 tokens per session scan A 60d92a70c5a4
changelog is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 343 once invoked, about $0.0001 per session on Opus 5.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-10-16.
Other commands, from other repositories
versioning
Universal version file discovery and sync. Works with any project structure.
ship
Complete PR workflow from commit to production with validation.
release-baseline
Makes a "cut" after a release: project state is documented as given, HANDOVER is archived and summarized, docs are split into Frozen/Active.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
release
Create a new release with version bump, changelog update, git tag, npm publish, and optional GitHub Release.