agentmods.dev

repo-native-alignment: Agent for Claude Code

.claude/agents/dev-pipeline-oversight.md

dev-pipeline-oversight is an agent for Claude Code from open-horizon-labs/repo-native-alignment. It costs 41 tokens per session (556 once invoked), scanned A, original, MIT.

A development workflow that runs dev-pipeline and then checks the merged pull request, a proposed code change, for review comments that were left unresolved.

In plain words
What is it for?
Use it to manage an issue through coding and merging, confirm an issue and draft pull request were created early, audit all comments afterward, and fix or document unresolved findings.
Why use it?
It catches review findings that the main shipping agent may have overlooked and verifies that required process steps happened.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is open-horizon-labs/repo-native-alignment's own configuration. It tells Claude Code how to work on repo-native-alignment itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything repo-native-alignment configures →

not rated 6repo 1mo ago A scan 41 tokens original MIT
View source ↗ open-horizon-labs/repo-native-alignment
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/open-horizon-labs/repo-native-alignment/main/.claude/agents/dev-pipeline-oversight.md
Clone the repo
git clone --depth 1 https://github.com/open-horizon-labs/repo-native-alignment

Made for: Claude Code.

Wrote 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.

agentmods badge for dev-pipeline-oversight

README.md
[![agentmods](https://agentmods.dev/badge/agents/open-horizon-labs/repo-native-alignment/dev-pipeline-oversight/github.svg)](https://agentmods.dev/agents/open-horizon-labs/repo-native-alignment/dev-pipeline-oversight)
Your own site
<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.

agentmods 80×15 button for dev-pipeline-oversight

Your own site · 80×15
<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>
Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 556 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.00556
Opus 5.5 $0.00016 $0.00222
Sonnet 5.5 $0.00008 $0.00111
Haiku 4.5 $0.00004 $0.00056

Measured 2mo ago against content hash ca100cb21174, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/agents/dev-pipeline-oversight.md · 61 lines

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.

  1. Fetch ALL PR comments:

    gh api repos/{owner}/{repo}/pulls/{pr}/comments --paginate
gh api repos/{owner}/{repo}/issues/{pr}/comments --paginate

  2. For each non-ship-agent comment, verify it was addressed:

    • Code change made? Commit that fixes it? Reply explaining why not?
    • If none: unaddressed.

  3. Priority: Critical=must fix. Major=must fix or document why not. Minor=fix if easy.

  4. If anything unaddressed: fix in a new branch fix: address review findings from #<PR>, push PR.

  5. Verify the mandatory independent final-diff review evidence:

    • A fresh, separate repo-local /review sub-agent posted explicit APPROVE
    • The comment identifies the reviewer task and exact reviewed commit SHA
    • The reviewed SHA equals the PR's final headRefOid at 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

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
Changes

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.

  1. 2mo ago First seen · 61 lines · 41 tokens per session scan A ca100cb21174

Subscribe to this mod's changes

dev-pipeline-oversight is an agent published in the GitHub repository open-horizon-labs/repo-native-alignment (6 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 556 once invoked, about $0.0002 per session on Opus 5.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.

Code review
Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

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…

genkovich/sdd · 81 tokens

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…

damusix/atomic-claude · 169 tokens