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/commands/marioepkone/pipelineiq/pipeline-team)<a href="https://agentmods.dev/commands/marioepkone/pipelineiq/pipeline-team"><img src="https://agentmods.dev/badge/commands/marioepkone/pipelineiq/pipeline-team/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/marioepkone/pipelineiq/pipeline-team"><img src="https://agentmods.dev/badge/commands/marioepkone/pipelineiq/pipeline-team.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.04714 |
| Opus 5 | $0.00000 | $0.02357 |
| Sonnet 5 | $0.00000 | $0.00943 |
| Haiku 4.5 | $0.00000 | $0.00471 |
Grade A, and why
pipeline-team 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 360 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrates the full implementation pipeline (impl-plan -> impl -> audit -> fix -> merge) across multiple pre-written specs simultaneously using Claude Code's agent teams feature. Specs run in parallel where dependencies allow; merges are serialized through the lead to preserve the worktree invariant. Replaces the pattern of manually running /pipeline N times in sequence.
Invocation: /pipeline-team [path-or-filter]
- No argument -> scans
specs/team/ - Argument with
/-> treated as directory path to scan - Argument without
/-> treated as filename filter inspecs/team/
Requires: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in env or settings.json, Claude Code >= 2.1.32.
Specs must be pre-written -- the interactive spec interview does not compose with parallelism. Split large specs with /spec-splitter first, then run this command.
The argument (if any) is: $ARGUMENTS
Resolve COMMANDS_PATH
Determine the absolute path to this plugin's commands/ directory.
Discovery order:
- Read
~/.claude/plugins/installed_plugins.json. Parse as JSON. Find any key matchingpipelineiq@*(match plugin name prefix, ignore marketplace suffix). If multiple matches: collect all entries across all matching keys, sort bylastUpdateddescending, take the first. Set COMMANDS_PATH = /commands. - If the registry file does not exist, is unreadable, or contains no
pipelineiq@*key: walk up from CWD looking for.claude-plugin/plugin.jsonwhere the adjacentcommands/directory containspipeline.md. If found: COMMANDS_PATH = <that commands/ directory> - If neither found: STOP with "Cannot locate PipelineIQ plugin. Ensure the plugin is installed via the plugin marketplace, or you are in the PipelineIQ repo."
Verify: check that COMMANDS_PATH/references/pipeline-team/ exists. Store COMMANDS_PATH as an absolute path for use in all subsequent phases.
Phase 0 -- Pre-flight Checks (Lead, Inline)
--- /pipeline-team: PRE-FLIGHT ---
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.
- 10d ago First seen · 360 lines · 0 tokens per session scan A 1ef4a3973516
pipeline-team is a command published in the GitHub repository MarioEpkOne/PipelineIQ (2 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,714 tokens. 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 commands, from other repositories
workflow-classify
Classify task size (S/M/L/XL) and recommend the appropriate workflow pipeline.
security-review
A security review procedure based on CWE, a list of common software weaknesses, and STRIDE, a method for identifying threats to a system.
slack-gif-creator
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
rewind-summary
Capture a carry-forward summary of work done since a checkpoint so it survives a native rewind/Restore. Run before rewinding.
analytics-review
Review analytics and recent commits, then create tasks.