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 TeamDzX/myllm-skills --skill changeloggit clone --depth 1 https://github.com/TeamDzX/myllm-skillsWrote 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/teamdzx/myllm-skills/changelog)<a href="https://agentmods.dev/skills/teamdzx/myllm-skills/changelog"><img src="https://agentmods.dev/badge/skills/teamdzx/myllm-skills/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/teamdzx/myllm-skills/changelog"><img src="https://agentmods.dev/badge/skills/teamdzx/myllm-skills/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.00028 | $0.00229 |
| Opus 5 | $0.00014 | $0.00114 |
| Sonnet 5 | $0.00006 | $0.00046 |
| Haiku 4.5 | $0.00003 | $0.00023 |
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 11d 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
Turn the user's raw list of commits/changes into clean release notes in the Keep a Changelog style.
Format:
## [<version>] - <YYYY-MM-DD>
### Added
- …
### Changed
- …
### Fixed
- …
### Removed
- …
### Deprecated
- …
### Security
- …
Rules:
- Group each change under the right heading; omit headings with no entries.
- Rewrite commit shorthand into clear, user-facing language ("Fixed crash when opening empty files", not "fix npe in FileView").
- One bullet per meaningful change; merge duplicates; drop noise (merge commits, formatting-only churn) unless notable.
- Use the version/date if the user gives them; otherwise leave
[Unreleased]and<YYYY-MM-DD>placeholders. - Lead with what matters most to users. Output only the changelog.
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.
- 11d ago First seen · 36 lines · 28 tokens per session scan A 460d8f75fe41
changelog is a skill published in the GitHub repository TeamDzX/myllm-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 229 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-notes-writing
Writes release notes that are clear, customer-friendly, and useful. Use when shipping needs a concise summary of changes and impact.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
clawhub-production-release
Run and verify ClawHub production deploys and stable ClawHub CLI npm releases. Use when deploying backend or frontend changes to clawhub.ai, dispatching the Deploy workflow, publishing a stable CLI tag, checking release prerequisites, or proving the exact production SHA and workflow outcome.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…
release-dry-run
Dry run for release: summarize changes since last release and suggest version bump.