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.
git clone --depth 1 https://github.com/Malo-T/claude-toolbeltWrote 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/plugins/malo-t/claude-toolbelt/slack-changelog)<a href="https://agentmods.dev/plugins/malo-t/claude-toolbelt/slack-changelog"><img src="https://agentmods.dev/badge/plugins/malo-t/claude-toolbelt/slack-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/plugins/malo-t/claude-toolbelt/slack-changelog"><img src="https://agentmods.dev/badge/plugins/malo-t/claude-toolbelt/slack-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
slack-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
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "slack-changelog",
"description": "Turns what changed in a release into a Slack changelog a non-technical audience can read — filtered to what they'd notice, one theme, one bullet per idea, no code vocabulary.",
"version": "1.0.0",
"license": "MIT",
"author": {
"name": "Malo Toanen"
},
"homepage": "https://github.com/Malo-T/claude-toolbelt/tree/main/plugins/slack-changelog"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 332 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 12 lines scan A e5661152719e
slack-changelog is a plugin published in the GitHub repository Malo-T/claude-toolbelt (2 stars, last pushed 19d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
dootask
A DooTask plugin toolkit for creating plugins, preparing releases, improving project instructions, and making Conventional Commits. Conventional Commits are a standard format for describing Git changes.
open-source
Collection of skills for open-source R and Python package developers.
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
issue-to-pr
Take a GitHub issue (bare, or tracked on a Project board) from triage to a merge-ready PR through a gated, worktree-isolated pipeline that scales its depth to the task and asks at most one batched question. The gates hold every run: design hardening, tests green, code review clean. Once you approve the PR in-session…
ship
Complete PR workflow from commit to production with validation.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes.