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/hotovo/aider-desk/update-changeloggit clone --depth 1 https://github.com/hotovo/aider-deskWhat 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 | $0.00011 | $0.00302 |
| Opus 5 | $0.00005 | $0.00151 |
| Sonnet 5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
update-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.
What it actually says
Update the CHANGELOG.md file by adding a new entry under the [UNRELEASED] section based on the current git diff.
This is the current CHANGELOG.md (first 20 lines):
!head -n 20 CHANGELOG.md
This is git diff HEAD to see what changes were made:
!git diff HEAD
Based on the git diff, generate a concise changelog entry following this format:
- description of the change in past tense (starting with lowercase)
Guidelines for generating the changelog entry:
- Use past tense (e.g., "added feature" not "add feature")
- Start with lowercase letter
- Be concise but descriptive
- Focus on user-visible changes
- Use appropriate verbs: added, fixed, improved, updated, removed, etc.
- If multiple related changes, combine them or create the most significant one
Examples of good entries:
- added support for custom commands in subfolders
- fixed issue with model selection not persisting
- improved performance of message rendering
- updated dependencies to latest versions
Now update the CHANGELOG.md file by inserting the generated entry as the last item under the [UNRELEASED] section. The changelog entry should be added to the end of the [UNRELEASED] section, after any existing entries in that section.
Do not read any files, just update based on given info.
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 · 35 lines · 11 tokens per session scan A 1015f62e7ad5
update-changelog is a command published in the GitHub repository hotovo/aider-desk (1,406 stars, last pushed yesterday), licensed Apache-2.0. It adds 11 tokens to every session and 302 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
gaai-audit
Show workspace audit log with filters and optional JSON export.
gaai-ask
Search workspace memory — ranked entries with 1-hop graph context (cognitive guarantee).
gaai-bootstrap
Initialize or refresh project context via Bootstrap Agent.
gaai-discover
Clarify intent & produce governed artefacts via Discovery Agent.
sugar-analyze
Analyze codebase for potential work and automatically create tasks.
sugar-review
Review and manage pending Sugar tasks interactively.