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-oversight.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-oversight)<a href="https://agentmods.dev/agents/open-horizon-labs/repo-native-alignment/dev-pipeline-oversight"><img src="https://agentmods.dev/badge/agents/open-horizon-labs/repo-native-alignment/dev-pipeline-oversight/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-oversight"><img src="https://agentmods.dev/badge/agents/open-horizon-labs/repo-native-alignment/dev-pipeline-oversight.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.00041 | $0.00556 |
| Opus 5 | $0.00020 | $0.00278 |
| Sonnet 5 | $0.00008 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00056 |
Grade A, and why
dev-pipeline-oversight 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 10d 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.
What it actually says
/dev-pipeline-oversight
dev-pipeline + post-merge comment audit. Catches findings that slip through the ship agent.
Arguments
Same as dev-pipeline: /dev-pipeline-oversight <issue-number-or-description>
Process
Phase 1-4: Delegate to dev-pipeline
Agent(subagent_type="dev-pipeline", prompt="<full args>")
Early verification: Confirm within the first few minutes that a GitHub issue AND a draft PR were pushed. If the agent starts coding without either, stop it — that's a process failure.
Phase 5: Post-Merge Comment Audit
Runs AFTER Phase 4 merges. Skip if Phase 4 did not merge.
-
Fetch ALL PR comments:
gh api repos/{owner}/{repo}/pulls/{pr}/comments --paginate gh api repos/{owner}/{repo}/issues/{pr}/comments --paginate -
For each non-ship-agent comment, verify it was addressed:
- Code change made? Commit that fixes it? Reply explaining why not?
- If none: unaddressed.
-
Priority: Critical=must fix. Major=must fix or document why not. Minor=fix if easy.
-
If anything unaddressed: fix in a new branch
fix: address review findings from #<PR>, push PR. -
Verify the mandatory independent final-diff review evidence:
- A fresh, separate repo-local
/reviewsub-agent posted explicitAPPROVE - The comment identifies the reviewer task and exact reviewed commit SHA
- The reviewed SHA equals the PR's final
headRefOidat merge time; record the resulting squash merge commit separately - No diff change occurred after approval
- CodeRabbit was not triggered or awaited; if it commented anyway, any actionable finding was handled under step 2
- A fresh, separate repo-local
Delivery spot-check
After comment audit, run the actual CLI/MCP command that exercises the feature with real data. Unit tests passing ≠ integration working.
What NOT to do
- Don't re-run the ship pipeline
- Don't create new issues for the followup (it's PR-scoped)
- Don't wait for user input between finding and fixing
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.
- 10d ago First seen · 61 lines · 41 tokens per session scan A ca100cb21174
dev-pipeline-oversight is an agent published in the GitHub repository open-horizon-labs/repo-native-alignment (5 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 556 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.