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 doancan/mags --skill mags-changeloggit clone --depth 1 https://github.com/doancan/magsWrote 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/doancan/mags/mags-changelog)<a href="https://agentmods.dev/skills/doancan/mags/mags-changelog"><img src="https://agentmods.dev/badge/skills/doancan/mags/mags-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/doancan/mags/mags-changelog"><img src="https://agentmods.dev/badge/skills/doancan/mags/mags-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.00014 | $0.00529 |
| Opus 5 | $0.00007 | $0.00264 |
| Sonnet 5 | $0.00003 | $0.00106 |
| Haiku 4.5 | $0.00001 | $0.00053 |
Grade A, and why
mags-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 10d 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
MAGS Changelog
Generate a changelog from git history, optionally saving it to the project.
Steps
1. Gather git context
Run git log --oneline -30 via Bash to get the recent commit history. Note the latest tag if any (git describe --tags --abbrev=0 2>/dev/null).
2. Generate changelog
Call mags_generate_changelog to produce a structured changelog from the project state and git history.
3. Display output
Present the changelog with stats:
== Changelog ==
Generated from <N> commits since <last tag or "initial commit">
## [Unreleased]
### Added
- <feature description>
- <feature description>
### Changed
- <change description>
### Fixed
- <fix description>
### Removed
- <removal description>
---
Stats: <N> features | <N> changes | <N> fixes | <N> removals
Use the Keep a Changelog format (Added, Changed, Fixed, Deprecated, Removed, Security). Omit empty sections.
4. Ask to save
Ask the user: "Save this changelog? Options:"
- Append to
docs/changelog/changes.md - Create release as
docs/changelog/v<version>.md(ask for version number) - Skip and just display
If the user chooses to save:
- Check if the target file exists with
mags_get_doc. - If it exists, prepend the new entry at the top using
mags_update_doc. - If it does not exist, create it with
mags_create_doc. - Confirm: "Changelog saved to
<path>."
Related commands:
| Command | Description |
|---|---|
/mags-status |
View project progress dashboard |
/mags-docs |
List all project documents |
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.
- 10d ago First seen · 80 lines · 14 tokens per session scan A c9a2badf507c
mags-changelog is a skill published in the GitHub repository doancan/mags (3 stars, last pushed 7mo ago), licensed MIT. It adds 14 tokens to every session and 529 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-31.
Other skills, from other repositories
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
ops-release
OPS on-demand: This skill should be used when the user asks to "release the plugin", "publish ops…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.