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 JeonJe/claude-pluginsnpx agentmods add plugins/jeonje/claude-plugins/ma-pipelinegit clone --depth 1 https://github.com/JeonJe/claude-pluginsWrote 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/jeonje/claude-plugins/ma-pipeline)<a href="https://agentmods.dev/plugins/jeonje/claude-plugins/ma-pipeline"><img src="https://agentmods.dev/badge/plugins/jeonje/claude-plugins/ma-pipeline.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
ma-pipeline 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 3d 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": "ma-pipeline",
"version": "1.0.0",
"description": "Quality-gated multi-agent delivery pipeline: ticket → PRD → tech design → per-project PLAN → plan review → worktree handoff → delegated implementation → code review → PR/MR",
"author": {
"name": "JeonJe",
"url": "https://github.com/JeonJe"
},
"repository": "https://github.com/JeonJe/claude-plugins",
"license": "MIT",
"keywords": ["claude-code", "plugin", "pipeline", "prd", "tech-design", "plan-review", "worktree", "delegation", "code-review", "merge-request"],
"skills": "./skills"
}
What it installs
The manifest is a name and a version. 8 skills, 2 agents travel with it, and installing the plugin installs all of them — 801 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.
- 3d ago First seen · 14 lines scan A e79cf6dc1888
ma-pipeline is a plugin published in the GitHub repository JeonJe/claude-plugins (3 stars, last pushed 29d 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
a11y-audit
Full accessibility audit with WCAG compliance checking.
backend-architect
Backend service architecture design with endpoint scaffolding.
dev-tooling
Three MCP servers for PHP and JavaScript operations plus an optional PHP language server. PHP (php-tooling): PHPStan, ECS, Rector, PHPUnit, PHPUnit coverage gap analysis, Symfony Console. Administration (js-admin-tooling): ESLint, Stylelint, Prettier, Jest, TypeScript, Vite builds. Storefront (js-storefront-tooling)…
bevy-plugin
Bevy game engine development - ECS, rendering, game architecture.
ryk
ryk safety hooks and skills for Claude Code.
development
Code development and quality assurance tools - analyze, test, fix, review.