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/pipelineiq)<a href="https://agentmods.dev/plugins/marioepkone/pipelineiq/pipelineiq"><img src="https://agentmods.dev/badge/plugins/marioepkone/pipelineiq/pipelineiq.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
pipelineiq 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",
"version": "1.3.0",
"description": "Closed-loop spec -> plan -> implement -> audit -> fix -> merge pipeline for Claude Code",
"author": {
"name": "Epkone",
"url": "https://github.com/Epkone"
},
"repository": "https://github.com/Epkone/PipelineIQ",
"license": "MIT",
"keywords": ["pipeline", "spec", "implementation", "audit", "code-review", "automation"],
"skills": "./commands/"
}
What it installs
The manifest is a name and a version. 10 commands, 6 agents travel with it, and installing the plugin installs all of them — 190 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command pipeline A 0 tokens
- Command pipeline-team A 0 tokens
- Command spec-splitter A 0 tokens
- Command impl A 0 tokens
- Command impl-plan A 0 tokens
- Command learnings-review A 0 tokens
- Command audit-implementation A 0 tokens
- Command fix A 0 tokens
- Command spec A 0 tokens
- Command CLAUDE A 0 tokens
- Agent auditor A 33 tokens
- Agent implementer A 31 tokens
- Agent planner A 31 tokens
- Agent re-auditor A 33 tokens
- Agent repair-agent A 33 tokens
- Agent fixer A 29 tokens
What ships with it
1 file beside plugin.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 · 14 lines scan A ce96a5f585f0
pipelineiq 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
prflow
Turn feature requests into review-ready pull requests: issue, implementation, tests, a review-and-fix loop, and docs. Runs locally or on GitHub Actions, and is built for complex brownfield repos. Each week its retrospective reads what you actually merged and proposes improvements to your skill extensions.
review-suite
Independent plan and delivery reviews with evidence-based verdicts.
opik-integrations-auditor
Audit, compare, and document Opik integrations across Python, TypeScript, and backend OTEL/API surfaces with a repeatable evidence-first workflow.
technical-deslop
Clean branch/staged diffs by removing AI-style slop and restoring repo-consistent style without changing behavior.
lets
Development workflow with session management, code review, and task tracking.
ticket-triage
Backlog-drain loop: rank the open tickets, dispatch the genuinely startable ones in parallel (worktree-isolated, role-briefed, honest width), verify and merge each result, and re-triage on every completion until the queue is empty or everything left needs the user.