Borrowing it
Nothing to install: this file belongs to open-horizon-labs/repo-native-alignment. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/open-horizon-labs/repo-native-alignment/main/.claude/agents/dev-pipeline.mdgit clone --depth 1 https://github.com/open-horizon-labs/repo-native-alignmentWrote 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/open-horizon-labs/repo-native-alignment/dev-pipeline)<a href="https://agentmods.dev/agents/open-horizon-labs/repo-native-alignment/dev-pipeline"><img src="https://agentmods.dev/badge/agents/open-horizon-labs/repo-native-alignment/dev-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/agents/open-horizon-labs/repo-native-alignment/dev-pipeline"><img src="https://agentmods.dev/badge/agents/open-horizon-labs/repo-native-alignment/dev-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.00033 | $0.00775 |
| Opus 5 | $0.00016 | $0.00387 |
| Sonnet 5 | $0.00007 | $0.00155 |
| Haiku 4.5 | $0.00003 | $0.00077 |
Grade A, and why
dev-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 8d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dev-pipeline
problem-statement → solution-space → execute → ship. Four phases, each gates the next.
Arguments
/dev-pipeline <issue-number-or-description>
Session File
Write all phase outputs to .oh/sessions/<issue-number>-dev.md. Include an ## RNA Tool Friction Log table — every Grep/Read used for code navigation after scan is a skipped friction event.
Phase 1: GitHub Issue (problem-statement)
Create the issue FIRST. It is the anchor for everything.
- If issue number given: read it, check for clear problem statement + acceptance criteria. Reframe with
oh-problem-statementagent if needed. - If description given: spawn
oh-problem-statementagent (do not skip or inline), thengh issue createwith the output.
Gate: No Phase 2 without acceptance criteria on a GitHub issue.
Phase 2: Branch + Draft PR → Solution Space
Push the PR IMMEDIATELY — before solution exploration. Progress must be visible from the start.
git checkout -b <issue-number>-<slug> maingit commit --allow-empty -m "wip: <title>"→git push -u origin→gh pr create --draft- Then spawn
oh-solution-spaceagent. Bias against Local Optimum solutions — if it involves intricate coordination or new lock protocols, step up to Reframe/Redesign. - Update PR description with chosen solution.
Gate: No Phase 3 without a draft PR pushed to remote.
Phase 3: Execute
- Set up worktree:
scripts/prep-worktree.sh .claude/worktrees/<issue> <branch>, setCARGO_TARGET_DIR=$PWD/target - Scan before coding:
repo-native-alignment scan --repo . --full— verify non-zero symbol count before touching any source file - Spawn
oh-executeagent with the session file as context - Push commits to PR branch. Tag with
[outcome:X]if relevant.
Gate: SALVAGE verdict → stop and surface to user.
Phase 4: Ship
Spawn the ship agent. Do NOT inline ship steps.
Agent(subagent_type="ship", prompt="/ship <PR-number>\n\nWORKTREE: <path>\nCARGO_TARGET_DIR: <path>/target")
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.
- 8d ago First seen · 76 lines · 33 tokens per session scan A cf1f4d0723fd
dev-pipeline is an agent published in the GitHub repository open-horizon-labs/repo-native-alignment (4 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 775 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.