Agent skill

Pipeline

Full development pipeline: create GitHub issue, plan, implement with agent team, verify (build+test), commit, push, close issue.

MITAuto-check passed

Install Pipeline

skills CLI

$ npx skills add spytensor/openmozi --skill pipeline -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install spytensor/openmozi pipeline --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/spytensor/openmozi.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pipeline .claude/skills/pipeline && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "pipeline" agent skill from https://github.com/spytensor/openmozi/tree/main/.claude/skills/pipeline into .claude/skills/pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/spytensor/openmozi/tree/main/.claude/skills/pipeline

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add spytensor/openmozi --skill pipeline -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install spytensor/openmozi pipeline --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spytensor/openmozi.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/pipeline .agents/skills/pipeline && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "pipeline" agent skill from https://github.com/spytensor/openmozi/tree/main/.claude/skills/pipeline into .agents/skills/pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add spytensor/openmozi --skill pipeline -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install spytensor/openmozi pipeline --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spytensor/openmozi.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/pipeline .cursor/skills/pipeline && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "pipeline" agent skill from https://github.com/spytensor/openmozi/tree/main/.claude/skills/pipeline into .cursor/skills/pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/spytensor/openmozi.git --path .claude/skills/pipeline

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add spytensor/openmozi --skill pipeline -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install spytensor/openmozi pipeline --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spytensor/openmozi.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/pipeline .gemini/skills/pipeline && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "pipeline" agent skill from https://github.com/spytensor/openmozi/tree/main/.claude/skills/pipeline into .gemini/skills/pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install spytensor/openmozi pipeline

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add spytensor/openmozi --skill pipeline -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/spytensor/openmozi.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/pipeline .github/skills/pipeline && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "pipeline" agent skill from https://github.com/spytensor/openmozi/tree/main/.claude/skills/pipeline into .github/skills/pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add spytensor/openmozi --skill pipeline -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install spytensor/openmozi pipeline --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/spytensor/openmozi.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/pipeline .opencode/skills/pipeline && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "pipeline" agent skill from https://github.com/spytensor/openmozi/tree/main/.claude/skills/pipeline into .opencode/skills/pipeline/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pipeline", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: pipeline
GitHub stars: 439
Token cost: ~549 tokens
SKILL.md length: 225 words
Files: 1
Skills in repo: 13
Repo updated: Aug 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Full development pipeline: create GitHub issue, plan, implement with agent team, verify (build+test), commit, push, close issue.

Works in 8 steps: Create GitHub Issue → Plan → Build Agent Team & Implement → …
You need to implement a feature
Calls git, gh and pnpm

What it does

Pipeline is an agent skill from spytensor/openmozi. Full development pipeline: create GitHub issue, plan, implement with agent team, verify (build+test), commit, push, close issue. Use when you need to implement a feature or fix end-to-end.

Its SKILL.md is about 550 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub. The repository describes itself as: A custom Agent OS built to be hackable, heavily inspired by OpenClaw. The licence is MIT.

When your agent uses it

You need to implement a feature

Example prompts

“/pipeline”

Workflow steps

8 steps, taken from the step headings in SKILL.md.

Create GitHub Issue
Plan
Build Agent Team & Implement
Review
Verify
Commit & Push
Close Issue
Cleanup

What it can do on your machine

Read from SKILL.md and the folder at commit ac46df0. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
- pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, gh and pnpm, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Pipeline loads about 549 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 225 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~49
When it runs · the whole SKILL.md, loaded when a task matches: ~549

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from spytensor/openmozi at commit ac46df0, republished under its MIT licence (© spytensor). 225 words, ~549 tokens.

Download SKILL.mdSave it as .claude/skills/pipeline/SKILL.md (or your agent's skills folder).

name: pipeline
description: Full development pipeline: create GitHub issue, plan, implement with agent team, verify (build+test), commit, push, close issue. Use when you need to implement a feature or fix end-to-end.
disable-model-invocation: true

Development Pipeline

Automate the full development lifecycle for a feature or fix described by $ARGUMENTS.

Workflow

Execute these steps in order. Stop and report if any step fails.

Step 1: Create GitHub Issue

bash

gh issue create --title "<concise title from $ARGUMENTS>" --body "<detailed description>"

Parse the returned URL to extract the issue number. Print it.

Step 2: Plan

Research the codebase to understand what files need changing
Design the implementation approach
Identify all files to modify/create
Write the plan to a file at .claude/plans/<issue-number>.md

Step 3: Build Agent Team & Implement

Use TeamCreate to create a team named after the issue
Break the plan into independent tasks using TaskCreate
Spawn agents in parallel using the Task tool with team_name parameter:
- Each agent handles one task (one file or one concern)
- Use subagent_type: "general-purpose" with mode: "bypassPermissions"
- Run agents in background when possible
Wait for all agents to complete by checking TaskList

Step 4: Review

Read the modified files to verify changes are correct
Check for obvious issues, missing imports, type errors

Step 5: Verify

Run build and tests:

bash

pnpm build
pnpm test

If build or tests fail:

Read the error output
Fix the issues directly
Re-run verification
Repeat until passing

Step 6: Commit & Push

bash

git add <changed files>
git commit -m "feat: <description> (#<issue-number>)

Co-authored-by: Mozi <MoziAI-co@users.noreply.github.com>"
git push origin main

Step 7: Close Issue

bash

gh issue close <issue-number> --comment "Implemented in <commit-hash>."

Step 8: Cleanup

Shut down all team agents via SendMessage with type: "shutdown_request"
Delete the team via TeamDelete
Report final summary: issue number, commit hash, files changed, test results

Files

Just SKILL.md in .claude/skills/pipeline of spytensor/openmozi.

Open the folder on GitHubat commit ac46df0

Compare with similar skills

Pipeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Pipeline compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Pipeline this skillspytensor/openmozi	439	—	~549	Automated safety check: Pass	MIT	2 mo ago
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	today
Diagnosing Superpowers Sessionsobra/superpowers	296k	3 repos	~1.7k	Automated safety check: Pass	MIT	today
GitHub Deep Researchbytedance/deer-flow	83k	5 repos	~1.3k	Automated safety check: Pass	MIT	today
Greplooponyx-dot-app/onyx	32k	4 repos	~3.3k	Automated safety check: Pass	MIT	today
Update V8 Versionopeninterpreter/openinterpreter	69k	2 repos	~845	Automated safety check: Pass	Apache-2.0	today

Similar skills

PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
69k GitHub starsUsed in 3 repos~4.2k tokens
DevelopmentAuto-check passed
Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
296k GitHub starsUsed in 3 repos~1.7k tokens
Agent WorkflowsAuto-check passed
GitHub Deep Research
bytedance/deer-flow
Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.
83k GitHub starsUsed in 5 repos~1.3k tokens
Research & ScienceAuto-check passed
Greploop
onyx-dot-app/onyx
Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.
32k GitHub starsUsed in 4 repos~3.3k tokens
DevelopmentAuto-check passed
Update V8 Version
openinterpreter/openinterpreter
Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.
69k GitHub starsUsed in 2 repos~845 tokens
DevOps & CloudAuto-check passed
Check PR
onyx-dot-app/onyx
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
32k GitHub starsUsed in 2 repos~2.3k tokens
DevelopmentAuto-check passed

Questions about Pipeline

What does Pipeline do?

Full development pipeline: create GitHub issue, plan, implement with agent team, verify (build+test), commit, push, close issue. Pipeline is an agent skill from spytensor/openmozi. Full development pipeline: create GitHub issue, plan, implement with agent team, verify (build+test), commit, push, close issue.

When should I use Pipeline?

Pipeline fits situations like: you need to implement a feature.

How do I install Pipeline in Claude Code?

Run `npx skills add spytensor/openmozi --skill pipeline -a claude-code`. Or copy the skill folder (.claude/skills/pipeline in spytensor/openmozi) into .claude/skills/pipeline in your project. Claude Code loads it when a task matches its description.

How do I install Pipeline in Codex?

Run `npx skills add spytensor/openmozi --skill pipeline -a codex`. Or copy the skill folder (.claude/skills/pipeline in spytensor/openmozi) into .agents/skills/pipeline in your project. Codex loads it when a task matches its description.

Can I use Pipeline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add spytensor/openmozi --skill pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pipeline, .gemini/skills/pipeline, .github/skills/pipeline and .opencode/skills/pipeline in your project.

What does Pipeline need to run?

Going by SKILL.md and its folder, Pipeline needs the command-line tools its instructions call (git, gh and pnpm).

Does Pipeline access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Pipeline safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Pipeline use?

Pipeline is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Pipeline use?

About 549 tokens (SKILL.md is roughly 2.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Pipeline?

Skills that share tags, products or a category with Pipeline: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pipeline?

spytensor (a GitHub user) maintains it in spytensor/openmozi, which has 439 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on August 7, 2026.

Source: spytensor/openmozi on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Pipeline

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Development Pipeline

Workflow

Step 1: Create GitHub Issue

Step 2: Plan

Step 3: Build Agent Team & Implement

Step 4: Review

Step 5: Verify

Step 6: Commit & Push

Step 7: Close Issue

Step 8: Cleanup

Files

Compare with similar skills

Similar skills

More from spytensor/openmozi

Related

Questions about Pipeline