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/MarioEpkOne/PipelineIQWrote 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/marioepkone/pipelineiq/marketplace)<a href="https://agentmods.dev/plugins/marioepkone/pipelineiq/marketplace"><img src="https://agentmods.dev/badge/plugins/marioepkone/pipelineiq/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
pipelineiq-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 7d 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": "pipelineiq-marketplace",
"description": "PipelineIQ pipeline commands for Claude Code",
"owner": {
"name": "Epkone"
},
"plugins": [
{
"name": "pipelineiq",
"description": "Closed-loop spec -> plan -> implement -> audit -> fix -> merge pipeline",
"category": "development",
"source": {
"source": "url",
"url": "https://github.com/MarioEpkOne/PipelineIQ.git"
}
}
]
}
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.
- 7d ago First seen · 19 lines scan A 512c2dc7e838
pipelineiq-marketplace is a plugin published in the GitHub repository MarioEpkOne/PipelineIQ (2 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
code-operations-plugin
Skills for code manipulation operations including line-based code transfer, bulk refactoring, and file analysis - converted from code-copy-mcp.
brainstorm-panel
Assemble a task-specific panel of role-specialized agents and run a generate-critique-refine loop until the work converges on a strong result.
tune-repo-beta
Audit and tighten a repo's CLAUDE.md and guardrails so Claude Code works faster and more accurately in it: verify CLAUDE.md against reality, tighten the verify loop, add missing static guardrails, cut permission friction.
implement-issue
Drive a GitHub issue from branch to pull request with a language and build-tool agnostic workflow.
claude-settings-manager
Manage Claude Code settings with JSONC support and schema extraction.
understanding
Understand a topic or a bug: minimal explanations and root-cause diagnosis.