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 commands/higoralves/orc/stack-prgit clone --depth 1 https://github.com/HigorAlves/orcWhat 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 | $0.00046 | $0.02784 |
| Opus 5 | $0.00023 | $0.01392 |
| Sonnet 5 | $0.00009 | $0.00557 |
| Haiku 4.5 | $0.00005 | $0.00278 |
Grade A, and why
stack-pr 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 2d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:stack-pr
Convert a single big branch into a stack of smaller, chained PRs. Use this when the size gate fires on /orc:ship, or anytime you've ended up with a 600-LOC branch and want to break it down before review.
Arguments
--smart— dispatch theorc-stack-analyzeragent to propose logical slices from the diff (rather than the default commit-based slicing). Use when commits are messy (WIP, fixups, no Conventional Commits).--base <branch>— target a non-default base (e.g.develop). Defaults toorigin/HEAD.--draft— open every PR in the stack as a draft.--max-loc <N>— override the per-slice LOC budget (default: 300).--repos a,b/--repo a/--all-repos/--this-repo— workspace-mode targeting. Seeorc:workspace-mode.
Workflow
Phase 0 — Detect context
!orc-workspace-detect --banner
Context is injected above (ORC_* vars are exported for any Bash you run — do not re-run detection). Per-slice budget resolution: orc-pr-size budget ${ARG_MAX_LOC:+--max-loc "$ARG_MAX_LOC"}; per-slice LOC: orc-pr-size loc --base <slice-base>.
In workspace mode, resolve targetRepos from flags or AskUserQuestion. The stack lives per repo; cross-repo stacking is intentionally out of scope.
Phase 1 — Detect tooling
if command -v gh-stack >/dev/null 2>&1; then
STACK_TOOL="gh-stack"
elif gh stack --help >/dev/null 2>&1; then
STACK_TOOL="gh-stack-ext"
else
STACK_TOOL="none"
fi
If none, present AskUserQuestion:
- Install — run
gh extension install github/gh-stack. Continue when complete. - Use plain-gh fallback — chain via
gh pr create --base <prev-branch>per layer. No extension needed. - Cancel.
Never auto-install.
Phase 2 — Verify preconditions
Invoke orc:verification-before-completion (tests pass, lint clean). Then per repo:
git status --porcelain # must be empty
git rev-list --merges "$base"..HEAD # must be empty
n_commits=$(git rev-list --count "$base"..HEAD) # must be ≥ 2
git rev-list "@{u}..HEAD" --count 2>/dev/null # should be 0; warn if not
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.
- 2d ago First seen · 272 lines · 46 tokens per session scan A b83036eecb75
stack-pr is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 5d ago), licensed MIT. It adds 46 tokens to every session and 2,784 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 commands, from other repositories
setup
Set up Postman MCP Server. Authenticate via OAuth or API key, verify connection, select workspace.
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
refine-title
深度分析 Issue 或 PR 内容,并将其标题重构为 Conventional Commits 格式.
get-flow-run
Inspect a Postman Flow run by its Run ID — per-block logs, failing block, and status.
warden-cost
Dollar accounting — what does each active rule actually save, in money? Translates the token-measured verdict into dollars using a price table and the agent's own token-type mix, with a per-session net and a break-even. Read-only; spends no tokens.
routine
Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…