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 natnew/awesome-ai-scientists --skill changeloggit clone --depth 1 https://github.com/natnew/awesome-ai-scientistsWrote 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/natnew/awesome-ai-scientists/changelog)<a href="https://agentmods.dev/skills/natnew/awesome-ai-scientists/changelog"><img src="https://agentmods.dev/badge/skills/natnew/awesome-ai-scientists/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/natnew/awesome-ai-scientists/changelog"><img src="https://agentmods.dev/badge/skills/natnew/awesome-ai-scientists/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.00079 | $0.00413 |
| Opus 5.5 | $0.00032 | $0.00165 |
| Sonnet 5.5 | $0.00016 | $0.00083 |
| Haiku 4.5 | $0.00008 | $0.00041 |
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 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
Changelog Skill
Workflow
- Run the script from the project root:
python skills/changelog/scripts/changelog.py
On macOS or Linux, substitute python3 if python is not on your PATH. On Windows, the bundled python launcher is correct. Claude Code can invoke either; pick whichever resolves to a Python 3 interpreter on your system.
-
The script handles both cases automatically:
- No CHANGELOG.md: reads full git history, writes the file with all dates
- CHANGELOG.md exists: finds the newest
## YYYY-MM-DDheading, fetches commits after that date, prepends new sections
-
Review the output, edit bullet wording if needed, then commit
CHANGELOG.mdas part of the merge commit.
Format
# Changelog
## 2026-03-31
- Add responsive design to layout and CSS
- Add Vitest test suite for components and routes
## 2026-03-30
- Initial project scaffold
- One
# Changelogtitle at the top - Date headings as
## YYYY-MM-DD, newest first - Each commit is one bullet; wording may be cleaned up manually after generation
Notes
- Run from the project root (same directory as
.git/) - Commit subjects come directly from
git log; clean them up manually if needed - The script is idempotent: re-running when nothing is new prints a message and exits without modifying the file
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 79 tokens per session scan A ad620d3b9d0f
changelog is a skill published in the GitHub repository natnew/awesome-ai-scientists (20 stars, last pushed 5d ago), licensed MIT. It adds 79 tokens to every session and 413 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-08-30.
Other skills, from other repositories
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
writing-modpack-changelog
Use when cutting a modpack release. Creates /docs/release-changelog.md if absent; appends a new version section with grouped changes. Triggers - 'cut a release', 'release notes', 'changelog', 'v1.2.3 changes', 'what changed since last version'.
Git CLI
Help with safe Git workflows (branching, rebasing, release tags) and troubleshooting.
run-work
Execute a work unit end-to-end: sequence tasks by dependency, implement, test between tasks, commit, and track progress. Use to deliver a complete feature in one session. Invoked as /agiflow:run-work . Uses getworkunit, listtasks, updatetask, getworkunitprogress.
claude-devfleet
Orchestrate multi-agent coding tasks via Claude DevFleet — plan projects, dispatch parallel agents in isolated worktrees, monitor progress, and read structured reports.
git-worktree-isolation
A Git workflow that gives each development task its own worktree, which is a separate working directory linked to a branch. It keeps parallel tasks and experiments apart from the main checkout.