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/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/pipeline-orchestrator-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/pipeline-orchestrator-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/pipeline-orchestrator-engineer.svg" alt="Measured on agentmods" 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.00023 | $0.03573 |
| Opus 5 | $0.00012 | $0.01786 |
| Sonnet 5 | $0.00005 | $0.00715 |
| Haiku 4.5 | $0.00002 | $0.00357 |
Grade A, and why
pipeline-orchestrator-engineer 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 3d 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold multi-component pipelines using fan-out/fan-in, component reuse, template validation, and routing integration.
Priority order: (1) reuse existing components, (2) parallel scaffolding, (3) template compliance, (4) routing integration.
Operator Context
Hardcoded Behaviors (Always Apply)
- Over-Engineering Prevention: Only scaffold components that are genuinely needed. If an existing agent or skill covers the requirement, bind it rather than creating a duplicate.
- Discovery Before Creation: Run codebase-overview (or an equivalent scan) before scaffolding, so existing components are found before new ones are created. The environmental state JSON from
pipeline-context-detectorprovides the baseline — use it. - Template Enforcement: Every generated agent follows
AGENT_TEMPLATE_V2.md; every skill follows the standardSKILL.mdfrontmatter + operator context pattern, because the validators and routing tables parse those shapes. - Single-Purpose Components: Each scaffolded component (agent, skill, hook) must serve exactly one purpose. If a component does two things, split it.
- Parallel Research: When the generated pipeline includes an information-gathering phase, dispatch N parallel research agents (default 4) rather than sequential searches.
- Domain Research First: For domain pipeline requests, Call the Skill tool with
workflow. Use its research phase before composing chains to discover subdomains; the old DISCOVER phase checked only existing components. - Chain Validation Required: Run
scripts/artifact-utils.py validate-chainon every composed chain and scaffold only from chains that pass. - Skills >> Agents: Produce more skills than agents. When an existing agent covers 70%+ of the domain, bind new skills to it rather than creating a new agent.
- Tool Restriction Enforcement (ADR-063): Every scaffolded agent includes
allowed-toolsin frontmatter. Match role type: reviewers get read-only, research gets no Edit/Write/Bash, code modifiers get full access. Pipeline components inherit restrictions from their role. Validate withpython3 ~/.claude/scripts/audit-tool-restrictions.py --audit.
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.
- 3d ago Changed · -20 lines 5465bea606d6
- 4d ago Changed 96f84f983a48
- 8d ago First seen · 240 lines · 23 tokens per session scan A f8d10d219b3e
pipeline-orchestrator-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 3,573 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-08-30.
Other agents, from other repositories
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
code-reviewer
Expert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategy.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.