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/drn/dots/changelognpx skills add drn/dots --skill changeloggit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/changelog)<a href="https://agentmods.dev/skills/drn/dots/changelog"><img src="https://agentmods.dev/badge/skills/drn/dots/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 | $0.00025 | $0.00720 |
| Opus 5 | $0.00013 | $0.00360 |
| Sonnet 5 | $0.00005 | $0.00144 |
| Haiku 4.5 | $0.00003 | $0.00072 |
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 4d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Current branch: !
git branch --show-current - Latest tag: !
git describe --tags --abbrev=0 2>/dev/null | head -1 - Recent commits (last 7 days): !
git log --oneline --since="7 days ago" 2>/dev/null | head -20
Arguments
$ARGUMENTS- Optional: time period to look back (e.g., "2 weeks", "since v1.2.0", "last 30 days", "2025-01-01..2025-02-01")
Your task
Generate a well-organized, human-readable changelog from recent git history.
Step 1: Determine the time range
If the user provided a time period in $ARGUMENTS, use it. Otherwise, ask the user what time period they want the changelog to cover. Suggest useful options based on the context above:
- Since a specific tag (if tags exist)
- Last N days/weeks
- A date range
- Since a specific commit
Step 2: Gather commits
Run git log for the chosen time range with full commit messages:
git log --format="%H%n%s%n%b%n---END---" <range>
If there are merge commits, also look at what was merged:
git log --merges --format="%H %s" <range>
If there are very few commits, also inspect the diffs to understand what changed:
git diff --stat <range>
Step 3: Analyze and categorize
Read through all commit messages and diffs. Group changes into categories. Use only categories that have entries — skip empty ones. Choose from:
- Added — new features, commands, tools, or capabilities
- Changed — modifications to existing behavior, UI updates, refactors
- Fixed — bug fixes
- Removed — deleted features, deprecated code removal
- Infrastructure — CI/CD, build system, dependency updates, tooling
- Documentation — README, docs, comments
Step 4: Write the changelog
Write a changelog that is:
- Grouped by category with clear headers
- Concise but meaningful — each entry should explain what and why, not just parrot the commit message
- Deduplicated — combine related commits into a single entry (e.g., a feature + its follow-up fix = one entry)
- Ordered by significance within each category
- Free of noise — omit trivial changes like typo fixes or formatting unless nothing else happened
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.
- 4d ago First seen · 93 lines · 25 tokens per session scan A cecbd178d51c
changelog is a skill published in the GitHub repository drn/dots (23 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 720 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…