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/donnfelker/donnfelker-plugin-marketplaceWrote 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/donnfelker/donnfelker-plugin-marketplace/generate-release-notes)<a href="https://agentmods.dev/plugins/donnfelker/donnfelker-plugin-marketplace/generate-release-notes"><img src="https://agentmods.dev/badge/plugins/donnfelker/donnfelker-plugin-marketplace/generate-release-notes/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/donnfelker/donnfelker-plugin-marketplace/generate-release-notes"><img src="https://agentmods.dev/badge/plugins/donnfelker/donnfelker-plugin-marketplace/generate-release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
generate-release-notes 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 2mo 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
{
"name": "generate-release-notes",
"description": "Generates release notes and changelogs from conventional commit messages parsed from git log history",
"version": "1.0.0"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 80 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.
- 2mo ago First seen · 6 lines scan A b2d9efc7731a
generate-release-notes is a plugin published in the GitHub repository donnfelker/donnfelker-plugin-marketplace (4 stars, last pushed 4mo 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.
generate-release-notes compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| generate-release-notesdonnfelker/donnfelker-plugin-marketplace | Plugin | 4 | 4mo ago | MIT | A | — | Claude Code |
| utility-toolspawbytes/skill-suites | Plugin | 116 | 3d ago | MIT | A | — | Claude Code |
| charonANcpLua/ancplua-claude-plugins | Plugin | 6 | 3d ago | MIT | A | — | Claude Code |
| atlas-publishfledgeling-co/fledgeling-plugins | Plugin | 2 | 8d ago | MIT | A | — | Claude Code |
| oat-publish-pythonOpen-Agent-Tools/General-OAT-Skills | Plugin | 3 | 1mo ago | Apache-2.0 | A | — | Claude Code |
| ooda-loop marketplacemataeil/OODA-loop | Plugin | 6 | 4mo ago | MIT | A | — | Claude Code |
| essentialsAgentSystemLabs/essentials | Plugin | 86 | 6mo ago | none | A | — | Claude Code |