AiderDesk is an open-source desktop platform that coordinates AI-assisted software development around the Aider coding tool, letting engineers inspect and control proposed changes. It is for professional developers who want AI help while retaining their existing editor, terminal, and Git workflow. Catalogue add-ons extend its controlled development workflow.
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/hotovo/aider-deskWrote 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/hotovo/aider-desk/update-changelog)<a href="https://agentmods.dev/commands/hotovo/aider-desk/update-changelog"><img src="https://agentmods.dev/badge/commands/hotovo/aider-desk/update-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/hotovo/aider-desk/update-changelog"><img src="https://agentmods.dev/badge/commands/hotovo/aider-desk/update-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.00011 | $0.00302 |
| Opus 5.5 | $0.00004 | $0.00121 |
| Sonnet 5.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 1mo 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
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.
- 1mo ago 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,457 stars, last pushed today), licensed Apache-2.0. It adds 11 tokens to every session and 302 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
prepare-release
Prepare a version release — follows project release config in .aicontext/release.md, runs first-time setup if config is missing.
release
Generate or update changelog and release notes from project history.
ship
Create a rich PR from planning artifacts (SUMMARY one-liners, requirement coverage, verification status).
release
Release guide version (CHANGELOG + VERSION + README + landing sync + commit + push).
update-infos-release
Update Claude Code releases tracking (guide + landing + version bump).