Borrowing it
Nothing to install: this file belongs to BrainDAO/adk-ts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BrainDAO/adk-ts/main/.claude/commands/adk-ts-changelog.mdgit clone --depth 1 https://github.com/BrainDAO/adk-tsWrote 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/braindao/adk-ts/adk-ts-changelog)<a href="https://agentmods.dev/commands/braindao/adk-ts/adk-ts-changelog"><img src="https://agentmods.dev/badge/commands/braindao/adk-ts/adk-ts-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/braindao/adk-ts/adk-ts-changelog"><img src="https://agentmods.dev/badge/commands/braindao/adk-ts/adk-ts-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.00000 | $0.00963 |
| Opus 5 | $0.00000 | $0.00481 |
| Sonnet 5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
adk-ts-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 12d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate changelog entries and community release notes for ADK-TS from git history and changesets.
Workflow
Step 1: Gather Changes
-
Find the last release tag:
git tag --sort=-version:refname | head -5 -
Read git log since last tag:
git log {LAST_TAG}..HEAD --oneline --no-merges -
Check for pending changesets: Read all
.mdfiles in.changeset/directory (excludingREADME.md). Each changeset file contains a package name, version bump type (patch/minor/major), and description. -
Read existing changelogs for format reference:
packages/adk/CHANGELOG.md(last 50 lines for format)packages/adk-cli/CHANGELOG.md(last 50 lines for format)
Step 2: Categorize Changes
Group all changes into these categories:
| Category | Description | Emoji |
|---|---|---|
| Breaking Changes | API changes, removed features, behavior changes | 🚨 |
| Features | New capabilities, new tools, new agents | ✨ |
| Bug Fixes | Corrections to existing behavior | 🐛 |
| Documentation | Doc pages, READMEs, examples | 📝 |
| Internal | Refactoring, dependencies, CI/CD, tests | 🔧 |
Step 3: Generate Changelog Entry
Format the changelog entry matching the existing style in packages/adk/CHANGELOG.md:
## {VERSION}
### Major Changes
- Description of breaking change ([commit-hash])
### Minor Changes
- Description of new feature ([commit-hash])
### Patch Changes
- Description of bug fix ([commit-hash])
Step 4: Draft Community Release Notes
Generate a developer-friendly release summary suitable for GitHub Releases, blog posts, or social media:
# ADK-TS {VERSION} Release
{1-2 sentence summary of the release theme}
## Highlights
- **{Feature name}**: {Brief description of what it enables}
- **{Feature name}**: {Brief description}
## Breaking Changes
{If any, describe what changed and how to migrate}
## Bug Fixes
- {Fix description}
## Full Changelog
See the [full changelog](https://github.com/IQAIcom/adk-ts/blob/main/packages/adk/CHANGELOG.md) for all changes.
---
**Get started:** `pnpm add @iqai/adk@{VERSION}`
📖 [Documentation](https://adk.iqai.com/) | 💬 [Discussions](https://github.com/IQAIcom/adk-ts/discussions) | 🛠️ [IQ Builders Telegram](https://t.me/+Z37x8uf6DLE3ZTQ8) | 📱 [IQ AI Telegram](https://t.me/IQAICOM)
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.
- 12d ago First seen · 113 lines · 0 tokens per session scan A 2afcd20bbabc
adk-ts-changelog is a command published in the GitHub repository BrainDAO/adk-ts (119 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 963 tokens. 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
lfe-archivist
Act as the Archivist for an LFE-compliant project. Use when a change is approved and needs documentation sync, changelog updates, or pipeline status cleanup.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
update-documentation
You are a release engineer responsible for maintaining the root-level CHANGELOG.md and verifying plugin READMEs. Analyze git changes, update the single CHANGELOG.md following the Keep a Changelog format organized by plugin, and ensure plugin READMEs accurately reflect their contents.
fire-update
Check for and apply plugin updates from GitHub repository.
release
Prepara e pubblica una nuova release del plugin mcp-legal-it. Bumpa la versione in tutti i manifest, aggiorna i changelog e la description con il conteggio tool corretto, crea il release branch, merge in main e tagga.
ship
Deliver completed work with validation and documentation.