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 skills/vgrss/acumen/changelognpx skills add VGrss/Acumen --skill changeloggit clone --depth 1 https://github.com/VGrss/AcumenWrote 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/vgrss/acumen/changelog)<a href="https://agentmods.dev/skills/vgrss/acumen/changelog"><img src="https://agentmods.dev/badge/skills/vgrss/acumen/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.00035 | $0.01009 |
| Opus 5 | $0.00017 | $0.00504 |
| Sonnet 5 | $0.00007 | $0.00202 |
| Haiku 4.5 | $0.00003 | $0.00101 |
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 5d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MANDATORY PREPARATION
Invoke /product-thinking — it contains the Context Gathering Protocol and the AI Slop Test. Follow the protocol before proceeding.
Mindset
A changelog is not a commit log. It's a story about what changed for users, written in their language. Engineers care about what was built. Users care about what they can do now. A good changelog bridges both — it's specific enough for engineers to recognize their work, and clear enough for users to understand the impact.
Step 1: Gather Parameters
Ask the user:
- Time range — what period does this changelog cover? Examples: "last 7 days", "last month", "since v2.1", "since 2026-03-01". If provided as the argument, use that.
- Format — text only, or text and video script? If video, the changelog will include a companion script suitable for a walkthrough recording.
Step 2: Analyze Changes
Pull PR and Commit History
Use git log to gather all commits and merged PRs in the specified time range. For each:
- Read the PR title, description, and linked issues
- Identify what changed from the user's perspective (not the implementation perspective)
- Group changes by theme, not by PR
Ground in Feature Context
Read .acumen/features.md to understand the business context behind each change:
- Which feature area does this change belong to?
- Is this a new capability, an enhancement, or a fix?
- Which persona benefits?
Read .acumen.md for product positioning — frame changes in terms of the product's value proposition, not its architecture.
Categorize
Group changes into:
- New — capabilities that didn't exist before
- Improved — existing capabilities that got better
- Fixed — things that were broken and are now working
- Changed — behavior changes that existing users should know about (potential breaking changes)
Drop changes that are purely internal (refactors, dependency updates, CI changes) unless they affect performance or reliability in a way users would notice.
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.
- 5d ago First seen · 119 lines · 35 tokens per session scan A f5db71b09d82
changelog is a skill published in the GitHub repository VGrss/Acumen (11 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 35 tokens to every session and 1,009 once invoked, about $0.0002 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 skills, from other repositories
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…