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/kylepelham/DriftWrote 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/kylepelham/drift/changelog)<a href="https://agentmods.dev/commands/kylepelham/drift/changelog"><img src="https://agentmods.dev/badge/commands/kylepelham/drift/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.00000 | $0.00698 |
| Opus 5 | $0.00000 | $0.00349 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
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 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.
This is a copy
100% identical to changelog — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Create UPCOMING_CHANGELOG.md from the structured changelog input below.
If UPCOMING_CHANGELOG.md already exists, ignore its current contents completely.
Do not preserve, merge, or reuse text from the existing file.
The input already contains the exact commit range since the last non-draft release.
The commits are already filtered to the release-relevant packages and grouped into
the release sections. Do not fetch GitHub releases, PRs, or build your own commit list.
The input may also include a ## Community Contributors Input section.
Before writing any entry you keep, inspect the real diff with
git show --stat --format='' <hash> or git show --format='' <hash> so you can
understand the actual code changes and not just the commit message (they may be misleading).
Do not use git log or author metadata when deciding attribution.
Rules:
- Write the final file with release sections in this order:
## Core,## TUI,## Desktop,## SDK,## Extensions - Only include sections that have at least one notable entry
- Within each release section, keep bug fixes grouped under
### Bugfixes - Keep other notable entries under
### Improvementswhen a section has bug fixes too - Omit empty subsections
- Keep one bullet per commit you keep
- Skip commits that are entirely internal, CI, tests, refactors, or otherwise not user-facing
- Start each bullet with a capital letter
- Prefer what changed for users over what code changed internally
- Do not copy raw commit prefixes like
fix:orfeat:or trailing PR numbers like(#123) - Community attribution is deterministic: only preserve an existing
(@username)suffix from the changelog input - If an input bullet has no
(@username)suffix, do not add one - Never add a new
(@username)suffix fromgit show, commit authors, names, or email addresses - If no notable entries remain and there is no contributor block, write exactly
No notable changes. - If no notable entries remain but there is a contributor block, omit all release sections and return only the contributor block
- If the input contains
## Community Contributors Input, append the block below that heading to the end of the final file verbatim - Do not add, remove, rewrite, or reorder contributor names or commit titles in that block
- Do not derive the thank-you section from the main summary bullets
- Do not include the heading
## Community Contributors Inputin the final file - Focus on writing the least words to get your point across - users will skim read the changelog, so we should be precise
Importantly, the changelog is for users (who are at least slightly technical), they may use the TUI, Desktop, SDK, Plugins and so forth. Be thorough in understanding flow on effects may not be immediately apparent. e.g. a package upgrade looks internal but may patch a bug. Or a refactor may also stabilise some race condition that fixes bugs for users. The PR title/body + commit message will give you the authors context, usually containing the outcome not just technical detail
<changelog_input>
!bun script/raw-changelog.ts $ARGUMENTS
</changelog_input>
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 · 50 lines · 0 tokens per session scan A e299dd8ca291
changelog is a command published in the GitHub repository kylepelham/Drift (20 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 698 tokens. A static security scan graded it A with 0 findings. It is 100% identical to changelog, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
publish
Publish oh-my-opencode to npm via GitHub Actions workflow.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.
changelog-update
Actualiza CHANGELOG.md automáticamente analizando los commits desde la última versión/release. Clasifica los cambios por tipo (feat, fix, docs, etc.) usando los commits convencionales del workspace. Opcionalmente sugiere bump de versión semántica. Delega la redacción final a tech-writer.
release
Run the iPolloWork release flow.
release
Verify, sweep docs, cut a version — then hand the release sequence back.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.