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.
/plugin marketplace add Aimeerrhythm/enterprise-change-workflownpx agentmods add plugins/aimeerrhythm/enterprise-change-workflow/marketplacegit clone --depth 1 https://github.com/Aimeerrhythm/enterprise-change-workflowWrote 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/aimeerrhythm/enterprise-change-workflow/marketplace)<a href="https://agentmods.dev/plugins/aimeerrhythm/enterprise-change-workflow/marketplace"><img src="https://agentmods.dev/badge/plugins/aimeerrhythm/enterprise-change-workflow/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
enterprise-change-workflow marketplace 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 5d 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": "enterprise-change-workflow",
"owner": {
"name": "Aimeerrhythm"
},
"plugins": [
{
"name": "ecw",
"source": {
"source": "url",
"url": "https://github.com/Aimeerrhythm/enterprise-change-workflow.git"
},
"description": "Enterprise change management workflow: risk classification, multi-domain collaborative analysis, requirements elicitation, adversarial spec review, implementation correctness verification, and business impact analysis"
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 5d ago First seen · 17 lines scan A 690c5d0d4e2a
enterprise-change-workflow marketplace is a plugin published in the GitHub repository Aimeerrhythm/enterprise-change-workflow (1 stars, last pushed 3mo 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
hashb
Dev workflow toolkit — 20 skills + domain-specific rules. Skills work for any project; domain context comes from rules organized by vertical.
i-have-adhd
Shape Claude Code output for an ADHD reader: lead with the next action, number steps, suppress tangents, restate state, make wins visible.
claude-code-workflows marketplace
Plugin marketplace listing 8 plugins: dev-workflows, dev-workflows-frontend, dev-workflows-fullstack, dev-skills, metronome.
dev-skills
Lightweight skills for users with existing workflows - coding best practices, testing principles, and design guidelines without recipe workflows or agents.
cloudflare-browser-rendering
Cloudflare Browser Rendering with Puppeteer/Playwright. Use for screenshots, PDFs, web scraping, or encountering rendering errors, timeout issues, memory exceeded.
hush
Trims command output, logs, and Claude's play-by-play before they pile up in the session, so long, noisy work stays quiet and readable. Install and forget — nothing to configure. Short questions with nothing to run cost a little more.