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 agentmods add skills/uta2000/feature-flow/merge-prsnpx skills add uta2000/feature-flow --skill merge-prsgit clone --depth 1 https://github.com/uta2000/feature-flowWrote 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/uta2000/feature-flow/merge-prs)<a href="https://agentmods.dev/skills/uta2000/feature-flow/merge-prs"><img src="https://agentmods.dev/badge/skills/uta2000/feature-flow/merge-prs.svg" alt="Measured on agentmods" 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.00046 | $0.03427 |
| Opus 5 | $0.00023 | $0.01714 |
| Sonnet 5 | $0.00009 | $0.00685 |
| Haiku 4.5 | $0.00005 | $0.00343 |
Grade A, and why
merge-prs 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 5d 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge-PRs — Ship Phase Orchestrator
Discover, order, and merge feature-flow PRs. Supports three invocation modes determined by $ARGUMENTS.
Announce at start: "Starting Ship phase — discovering feature-flow PRs..."
Mode Detection
Inspect $ARGUMENTS:
| Pattern | Mode | Example |
|---|---|---|
Contains PR numbers (e.g. 185 186) |
Standalone | merge-prs 185 186 |
Contains all open |
Standalone | merge-prs all open |
Contains epic N |
Standalone | merge-prs epic 175 |
Equals feature-flow |
Cross-session | merge-prs feature-flow |
Standalone Mode
Accepts explicit PR targets:
| Argument pattern | Behavior |
|---|---|
185 186 |
Merge PRs #185 and #186 in the given order |
all open |
Query all open PRs on current base branch; merge in optimal order |
epic 175 |
Query PRs linked to issue #175 via body/title; merge in optimal order |
For all open:
gh pr list --base <current_branch> --state open --json number,title,headRefName,mergeable,statusCheckRollup
For epic N:
gh pr list --state open --json number,title,body --jq "[.[] | select(.body | test(\"#N\"))]"
For all open and epic N: execute Step 3 (dependency analysis + merge order), then Step 4 (sequential merge) and Step 5 (summary) as described in the sections below.
For explicit PR numbers (e.g. 185 186): skip Step 3 — the user specified the order. Execute Step 4 and Step 5 directly.
Cross-Session Mode
Argument: feature-flow
Discover all PRs labeled feature-flow:
gh pr list --label feature-flow --state open --json number,title,headRefName,baseRefName,mergeable,statusCheckRollup
Then execute Step 3 (merge order), Step 4 (sequential merge), and Step 5 (summary) as described in the sections below.
Step 3: Determine Merge Order
Read references/dependency-analysis.md to perform cross-PR import dependency analysis before applying heuristics.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/dependency-analysis.md 11 KB
- references/fixtures/metadata-block-absent.md 704 B
- references/fixtures/metadata-block-happy.md 1.8 KB
- references/fixtures/metadata-block-minimal.md 980 B
- references/fixtures/metadata-block-unknown-version.md 1.1 KB
- references/fixtures/metadata-block-unparseable.md 902 B
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.
- 5d ago First seen · 276 lines · 46 tokens per session scan A 343236fdcd3e
merge-prs is a skill published in the GitHub repository uta2000/feature-flow (4 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 3,427 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…