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.
npx skills add hamzaPixl/pixl-ai --skill multi-agent-pipelinegit clone --depth 1 https://github.com/hamzaPixl/pixl-aiWrote 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/skills/hamzapixl/pixl-ai/multi-agent-pipeline)<a href="https://agentmods.dev/skills/hamzapixl/pixl-ai/multi-agent-pipeline"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/multi-agent-pipeline/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/skills/hamzapixl/pixl-ai/multi-agent-pipeline"><img src="https://agentmods.dev/badge/skills/hamzapixl/pixl-ai/multi-agent-pipeline.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.00061 | $0.00445 |
| Opus 5.5 | $0.00024 | $0.00178 |
| Sonnet 5.5 | $0.00012 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
multi-agent-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 1mo 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
Overview
Scaffolds a multi-agent LLM pipeline with an orchestrator that coordinates specialized domain agents. Produces structured output with type safety.
Step 1: Discovery
- Understand the pipeline's purpose and domain areas
- Identify how many agents are needed and their specializations
- Determine the orchestration pattern (sequential, parallel, map-reduce)
- Define input/output schemas
Step 2: Base Agent
- Create the base agent class/interface
- Define the agent contract (input, process, output)
- Add LLM provider abstraction (support multiple providers)
- Implement structured output parsing
Step 3: Domain Agents (Parallel)
For each identified domain area:
- Create a specialized agent with domain-specific system prompt
- Define the agent's input/output schema
- Add domain-specific tools and knowledge
- Test the agent in isolation
Step 4: Orchestrator
- Build the orchestrator that coordinates domain agents
- Implement the chosen orchestration pattern
- Add error handling and retry logic
- Wire input routing and output aggregation
Step 5: Runner
- Create the pipeline entry point
- Add configuration for LLM provider, model, temperature
- Implement logging and tracing
- Add cost tracking
Step 6: Verify
- Each domain agent produces valid output in isolation
- Orchestrator correctly routes to agents
- Full pipeline runs end-to-end
- Structured output matches expected schema
- Error handling works (agent failure, timeout)
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.
- 1mo ago First seen · 58 lines · 61 tokens per session scan A faee24bcead7
multi-agent-pipeline is a skill published in the GitHub repository hamzaPixl/pixl-ai (2 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 445 once invoked, about $0.0002 per session on Opus 5.5. 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-09-03.
Other skills, from other repositories
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
finetuning
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file…