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/RealDougEubanks/ClaudeMarketplaceWrote 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/realdougeubanks/claudemarketplace/changelog-generator)<a href="https://agentmods.dev/plugins/realdougeubanks/claudemarketplace/changelog-generator"><img src="https://agentmods.dev/badge/plugins/realdougeubanks/claudemarketplace/changelog-generator.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
changelog-generator 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 8d 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": "changelog-generator",
"version": "1.3.0",
"description": "Generates a structured CHANGELOG.md following Keep a Changelog format from git history and ABD handoff artifacts. Prepends new version sections to existing changelogs.",
"author": {
"name": "Doug Eubanks",
"url": "https://github.com/RealDougEubanks"
},
"repository": "https://github.com/RealDougEubanks/ClaudeMarketplace",
"homepage": "https://github.com/RealDougEubanks/ClaudeMarketplace",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 37 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.
- 8d ago First seen · 13 lines scan A 57561a984a46
changelog-generator is a plugin published in the GitHub repository RealDougEubanks/ClaudeMarketplace (1 stars, last pushed 2mo 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
github-workflow
Git commit, PR creation, review, and merge skills following Conventional Commits.
ship
Complete PR workflow from commit to production with validation.
swarm-skill
Multi-agent codebase audit skill for Claude Code — spawns parallel subagents (security, performance, tests, architecture, dead-code) and synthesizes their findings into a prioritized action plan.
beecount-release
A release workflow for BeeCount projects that coordinates version tags, change logs, website updates and video copy across two code repositories. A release is the process of publishing a new software version.
claude-plugin-repo-ci-release
Wire up CI validation and automatic release-cutting for a Claude Code plugin or marketplace repo (one with a .claude-plugin/marketplace.json and plugins/). Adds two GitHub Actions — a structure validator on every PR/push, and a release-on-version-bump job that cuts a GitHub Release whenever VERSION changes — plus the.
dev-pipeline
A 5-phase development pipeline (requirement engineering, system architecture, task generation, verified implementation, code review) with an optional QA gate (plan-qa + execute-qa) for changes that have a running surface worth driving — independent of /review, run sequentially or in parallel at the developer's…