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/raulvidis/openclaw-multi-agent-kit/changeloggit clone --depth 1 https://github.com/raulvidis/openclaw-multi-agent-kitWrote 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/raulvidis/openclaw-multi-agent-kit/changelog)<a href="https://agentmods.dev/commands/raulvidis/openclaw-multi-agent-kit/changelog"><img src="https://agentmods.dev/badge/commands/raulvidis/openclaw-multi-agent-kit/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.00015 | $0.00309 |
| Opus 5 | $0.00008 | $0.00154 |
| Sonnet 5 | $0.00003 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
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 6d 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
Curate the user-facing changes since the last release into ## [Unreleased].
This is the input to release — run it before, not during, a release.
- Pick baseline: $1 if given, else !
git describe --tags --abbrev=0 2>/dev/null || echo "(no tags — use full history)" - Collect commits since baseline: review
git log <baseline>..HEAD --oneline --reverse. Skim diffs where impact is unclear. - Curate user-facing entries only:
- Include: shipped features, fixes, breaking changes, notable UX/behavior changes.
- Exclude: internal refactors, typo-only edits, dep bumps with no user impact, anything added then removed in the same window.
- Order by impact: breaking → features → fixes → misc.
- Add
#123PR/issue refs when known; never paste raw commit hashes.
- Edit
CHANGELOG.md: ensure## [Unreleased]exists at the top; append bullets under it, matching existing style (one bullet per entry, one line, past-tense, code in backticks). Do not hard-wrap long bullets. - Sanity check: renders cleanly, no duplicates, concise wording. Do not commit unless asked. Baseline hint: $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.
- 6d ago First seen · 18 lines · 15 tokens per session scan A 8857ca22cf6d
changelog is a command published in the GitHub repository raulvidis/openclaw-multi-agent-kit (395 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 309 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
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
Create a release branch, run changeset version, review changelog, and prepare PR.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
release
Walk the llmwiki release process step by step.
ship
Ship is the operational release-prep flow for a connected project repo.