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 Insajin/autopus-adk --skill agent-pipelinegit clone --depth 1 https://github.com/Insajin/autopus-adkWrote 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/insajin/autopus-adk/agent-pipeline)<a href="https://agentmods.dev/skills/insajin/autopus-adk/agent-pipeline"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/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/insajin/autopus-adk/agent-pipeline"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/agent-pipeline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00010 | $0.03946 |
| Opus 5 | $0.00005 | $0.01973 |
| Sonnet 5 | $0.00002 | $0.00789 |
| Haiku 4.5 | $0.00001 | $0.00395 |
Grade A, and why
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 12d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OMP Native Agent Pipeline
This is the default multi-agent execution contract for
/auto go SPEC-ID [--execution-owner omp|orca] on OMP.
Autopus owns phase and quality policy; exactly one selected owner owns the task DAG.
Activation
| Flag | Execution |
|---|---|
omitted --execution-owner |
owner omp, receipt source default |
--execution-owner omp |
owner omp, receipt source explicit |
--execution-owner orca |
owner orca, receipt source explicit |
--solo |
owner omp current session performs the work directly |
--team |
owner omp task batch with explicit Lead/Builder/Guardian responsibilities |
--multi |
selected owner's normal gates plus risk-tiered provider dissent review |
The team and provider axes are orthogonal:
--teamselects ownerompnativetaskbatch with explicit Lead/Builder/Guardian responsibilities.--multiselects provider-diverse planning and review, not team execution topology.--team --multicomposes team execution with provider-diverse planning and review.- without
--teamor--solo, ownerompuses the default nativetaskbatch pipeline. --teamconflicts with--soloand ownerorca.- Lead, Builder, and Guardian coordinate only through native
task,hub, andtodo; the main OMP session owns the checklist and DAG.
Parse the owner exactly once before any task, DAG-owning todo, OMP subprocess, or Orca
Run effect. Reject repeated, mixed, case-shifted, whitespace-padded, and aliased values; never
fuzzy-correct or silently fall back. Omission alone selects omp. --solo and --team are
OMP-only topology flags and conflict with owner orca.
Persist .autopus/pipeline-state/<SPEC-ID>.execution-owner.json as a body-free
pipeline_execution_owner_receipt.v1: owner, default|explicit source, reason, SPEC/run
identity, checked_at, and verification_status only.
- Owner
ompuses native OMPtask,hub, andtodoand must not create an Orca Run. - Owner
orcamust not create an OMP task/todo DAG. Run and readorca skills get orchestration --full, then use that current contract to create and supervise one durable cross-worktree Run. A plain full handoff does not satisfy this topology. auto pipeline run SPEC-ID --platform omp --execution-owner orcaruns the tier integrity gate and persistspipeline_execution_owner_receipt.v1before any Run, worker, or provider session exists, then executes the pipeline phases on supervised Orca workers. Never retry a failure as owneromp.
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.
- 12d ago First seen · 324 lines · 10 tokens per session scan A 29ab7c139c1a
agent-pipeline is a skill published in the GitHub repository Insajin/autopus-adk (111 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 3,946 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 skills, from other repositories
automations
Create, inspect, edit, archive, delete, run, and search scheduled or executable automation assets.
job
Execution behavior for one saved automation job running in a fresh agent conversation.
api-interface-design
Use when designing public APIs, module boundaries, provider adapters, tool schemas, or data contracts.
Using OmniForge Framework
Primary guide for using OmniForge CLI, MCP Server, workflows, and agent skills effectively.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
windows-deployment
Deploy FastAPI + React/Vite apps to Windows Server with NSSM services, reverse proxy (IIS or nginx), and git-pull workflow. Use when deploying any web app to a Windows prod server, setting up NSSM services, configuring IIS or nginx reverse proxy, making code environment-aware for dev/prod, or troubleshooting prod…