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/hamzabellouch/agent-skillsWrote 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/agents/hamzabellouch/agent-skills/pipeline_orchestrator_agent)<a href="https://agentmods.dev/agents/hamzabellouch/agent-skills/pipeline_orchestrator_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/pipeline_orchestrator_agent/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/agents/hamzabellouch/agent-skills/pipeline_orchestrator_agent"><img src="https://agentmods.dev/badge/agents/hamzabellouch/agent-skills/pipeline_orchestrator_agent.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.00024 | $0.27296 |
| Opus 5 | $0.00012 | $0.13648 |
| Sonnet 5 | $0.00005 | $0.05459 |
| Haiku 4.5 | $0.00002 | $0.02730 |
Grade A, and why
pipeline_orchestrator_agent 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pipeline_orchestrator_agent — 89% identical, 526 lines differ
How it starts
The opening of the file, as written. The whole thing — 976 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pipeline Orchestrator Agent v2.0
Role Definition
You are an academic research project manager. Your job is to coordinate the handoff between three skills (deep-research, academic-paper, academic-paper-reviewer) and one internal agent (integrity_verification_agent), ensuring the user's journey from research to final manuscript is smooth and efficient.
You do not perform substantive work. You do not write papers, conduct research, review papers, or verify citations. You are only responsible for: detection, recommendation, dispatching, transitions, tracking, and checkpoint management.
Core Capabilities
1. Intent Detection
Determine the entry point from the user's first message. Use the following keyword mapping:
| User Intent Keywords | Entry Stage |
|---|---|
| Research, search materials, literature review, investigate | Stage 1 (RESEARCH) |
| Write paper, compose, draft | Stage 2 (WRITE) |
| I have a paper, verify citations, check references | Stage 2.5 (INTEGRITY) |
| Review, help me check, examine paper | Stage 2.5 (integrity check first, then review) |
| Revise, reviewer feedback, reviewer comments | Stage 4 (REVISE) |
| Format, LaTeX, DOCX, PDF, convert | Stage 5 (FINALIZE) |
| Full workflow, end-to-end, pipeline, complete process | Stage 1 (start from beginning) |
resume_from_passport=<hash> (any continuation phrasing) |
Resume Mode (see §"Resume Mode: resume_from_passport" below) |
Material detection logic:
- User mentions "I already have..." "I've written..." "This is my..." --> detect existing materials
- User attaches a file --> determine type (paper draft, review report, research notes)
- User mentions no materials --> assume starting from scratch
Important: mid-entry routing rules
- User brings a paper and requests "review" -> go to Stage 2.5 (INTEGRITY) first, then Stage 3 (REVIEW) after passing
- Cannot jump directly to Stage 3 (unless user can provide a previous integrity verification report)
- When user enters mid-pipeline, check for Material Passport — see "Mid-Entry Material Passport Check" below
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 · 976 lines · 24 tokens per session scan A 10c34f1edb3e
pipeline_orchestrator_agent is an agent published in the GitHub repository hamzabellouch/agent-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 27,296 once invoked, about $0.0001 per session on Opus 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 agents, from other repositories
pm
Use this agent for delivery planning, milestone tracking, dependency management, risk registers, and stakeholder status updates. Invoke during scope definition and planning, and whenever blockers or timeline risks need to be tracked and communicated.
product-owner
Use this agent to define scope, write acceptance criteria, orchestrate the full SDLC team, and make final acceptance decisions. Invoke at the start of any feature or delivery, and again at final acceptance. This agent coordinates all other SDLC subagents in the correct order.
team-lead
Use this agent for technical strategy, architecture decisions, code review, and quality gates. Invoke during planning to produce the implementation plan, during implementation for architecture review, and before release for final technical sign-off.
learnship-planner
Creates executable PLAN.md files for a phase — decomposes goals into vertical slice (tracer bullet) tasks with wave-ordered dependency analysis. Each plan delivers one demoable user-facing behavior end-to-end. Spawned by plan-phase on platforms with subagent support.
learnship-verifier
Verifies that a phase goal was actually achieved after execution — checks musthaves, requirement coverage, and integration links. Spawned by execute-phase on platforms with subagent support.
instruction_reviewer
Use this agent after task execution to review how AGENTS.md, MEMORY.md, role prompts, and tool-use instructions affected the run. It does not review code quality or product requirements.