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 ApiliumCode/mayros --skill changelog-trackergit clone --depth 1 https://github.com/ApiliumCode/mayrosWrote 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/apiliumcode/mayros/changelog-tracker)<a href="https://agentmods.dev/skills/apiliumcode/mayros/changelog-tracker"><img src="https://agentmods.dev/badge/skills/apiliumcode/mayros/changelog-tracker/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/apiliumcode/mayros/changelog-tracker"><img src="https://agentmods.dev/badge/skills/apiliumcode/mayros/changelog-tracker.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.00018 | $0.00549 |
| Opus 5.5 | $0.00007 | $0.00220 |
| Sonnet 5.5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
changelog-tracker 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
changelog-tracker
Monitor version changes with semantic versioning analysis and breaking change detection across changelogs, release notes, and dependency updates.
When to Use
Use when tracking version updates across dependencies, reviewing changelogs for breaking changes, or auditing release notes before upgrading. The skill parses semver strings, classifies bump types, and scans for 7 breaking change indicators.
Semver Classification
| Bump Type | Meaning |
|---|---|
| Major (X.0.0) | Breaking change |
| Minor (0.X.0) | New feature (backward compatible) |
| Patch (0.0.X) | Bug fix |
Breaking Change Indicators
| # | Pattern | Description |
|---|---|---|
| 1 | "breaking change" / "BREAKING" | Explicit breaking change declaration |
| 2 | "removed" + API term | Removal of API surface (endpoint, method, function, field) |
| 3 | "deprecated" + "removed" | Previously deprecated item now removed |
| 4 | "incompatible" / "not backward compatible" | Explicit incompatibility statement |
| 5 | "migration required" / "migrate" | Migration needed for upgrade |
| 6 | "renamed" + API term | API surface renamed |
| 7 | "changed signature" / "new parameter required" | Function signature changes |
Instructions
- Recall previous changelog history with
skill_memory_contextusing predicatechangelog:history - The skill scans query results for semver version strings and breaking change indicators
- Breaking changes are asserted with
skill_assertusing predicatechangelog:breaking-changewith proof required - Version updates are recorded with predicate
changelog:version-updatewithout proof - Query changelog history to track version progression and breaking change frequency over time
What ships with it
9 files 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 · 57 lines · 18 tokens per session scan A 3ce55141c882
changelog-tracker is a skill published in the GitHub repository ApiliumCode/mayros (13 stars, last pushed 3mo ago), licensed MIT. It adds 18 tokens to every session and 549 once invoked, about $0.0001 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
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.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.
release-readiness-check
Verify all prerequisites are met before a release by checking PRs, CI/CD status, environment health, and blocking issues across GitHub, ArgoCD, and Jira. Use before cutting a release, deploying to production, or during release planning.