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 skills add tobihagemann/turbo --skill update-changeloggit clone --depth 1 https://github.com/tobihagemann/turboWrote 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/skills/tobihagemann/turbo/update-changelog)<a href="https://agentmods.dev/skills/tobihagemann/turbo/update-changelog"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/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/skills/tobihagemann/turbo/update-changelog"><img src="https://agentmods.dev/badge/skills/tobihagemann/turbo/update-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00068 | $0.00458 |
| Opus 5.5 | $0.00027 | $0.00183 |
| Sonnet 5.5 | $0.00014 | $0.00092 |
| Haiku 4.5 | $0.00007 | $0.00046 |
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 Changelog
Update the Unreleased section of the changelog based on the current changes.
Step 1: Run /changelog-rules Skill
Run the /changelog-rules skill to load shared changelog conventions.
Step 2: Check for Changelog
Use git rev-parse --show-toplevel to find the repository root. Look for the changelog file per /changelog-rules. If it does not exist, skip this skill. Do not create it.
Step 3: Analyze the Changes
Determine what changed:
- Read
git diff --cachedfor staged changes - If nothing is staged, read
git difffor unstaged changes - Use the conversation context for the intent behind the changes
Step 4: Assess Changelog-Worthiness
Apply the /changelog-rules changelog-worthiness and net-delta criteria. Skip fixes to code introduced by the same branch or PR.
If no changes are changelog-worthy, skip this skill.
Step 5: Check Existing Unreleased Entries
Read the current Unreleased section of the changelog. Look for entries that relate to the same feature or fix. This prevents duplicates across multiple commits for the same body of work.
- If an existing entry covers the same change, update its wording only if the current commit meaningfully extends or refines the feature. Do not add a duplicate entry.
Step 6: Update the Unreleased Section
Add or update entries in the Unreleased section following /changelog-rules conventions. Create subsection headers as needed (e.g., ### Added).
Then use the TaskList tool and proceed to any remaining task.
Rules
- Never modify released version sections. Only the Unreleased section is in scope.
- Do not stage the modified file. Staging is handled separately.
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 · 48 lines · 68 tokens per session scan A 1a6e2e5a5816
update-changelog is a skill published in the GitHub repository tobihagemann/turbo (417 stars, last pushed 4d ago), licensed MIT. It adds 68 tokens to every session and 458 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
changelog-generator
Convierte un git log, lista de commits o notas de lanzamiento en un changelog pulido orientado al usuario. Usa cuando estés escribiendo notas de versión, generando una entrada en CHANGELOG.md o documentando qué cambió en una versión. Produce una sección de changelog estructurada con encabezado de versión, cambios…
release-notes-from-git-log
Turn a git log into user-facing release notes grouped by feature and fix. Use when asked for release notes from this git log, a changelog entry from these commits, or to turn commits into release notes. Produces a grouped changelog with one line per change and a short headline.
antigravity-maintainer-batch-release
Run protected AAS maintainer sweeps, PR merge batches, canonical sync, Core preview checks, and scripted releases. Use for repository maintenance, main alignment, CLI/MCP/Workbench changes, or release work; not ordinary contribution tasks.
git-workflow
Use for branching, committing, history repair, and release hygiene. Covers atomic commits, rebase versus merge, bisect, reflog recovery, and undoing mistakes safely. Trigger on "undo my last commit", "i messed up a rebase", "squash these commits", "find which commit broke this". Do not use for pipeline and deploy…
changelog
Use when writing a changelog or release notes. Covers what belongs in one, writing for users rather than for git, semantic versioning, and documenting breaking changes so nobody is surprised. Trigger on "write release notes for v2.3", "update the changelog", "is this a major or minor version bump". Do not use for…
ship-plugin
Use when packaging skill files into this department plugin and shipping to GitHub, whether first-time setup or adding/updating skills in an existing plugin. Handles intake, structuring, local checks, commit, and PR.