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/setupgit 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.00050 | $0.02019 |
| Opus 5 | $0.00025 | $0.01009 |
| Sonnet 5 | $0.00010 | $0.00404 |
| Haiku 4.5 | $0.00005 | $0.00202 |
Grade A, and why
setup 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:setup
Scaffold the per-repo configuration that orc's tracker-aware surfaces assume:
- Issue tracker — where issues live and how to create/query them →
docs/agents/issue-tracker.md - Triage labels — the label vocabulary for the triage state machine →
docs/agents/triage-labels.md - Domain docs — where
CONTEXT.mdand ADRs live, and the consumer rules for reading them (perorc:domain-modeling) →docs/agents/domain.md
These files are read by orc:to-issues, orc:to-prd, /orc:triage, /orc:wayfinder, and the Jira adapters (orc:jira-cli, orc:evidence-publish) — the tracker choice recorded here decides whether they call gh, acli, or write local markdown.
This is a prompt-driven interview, not a deterministic script: explore, present what you found, confirm, then write. Run once per repo. Re-run only to switch trackers or restart from scratch — day-to-day edits go straight into docs/agents/*.md.
Arguments
--tracker github|jira|local— pre-answer Section A; the interview skips the tracker question and only confirms details (project key for Jira, directory for local).
Workflow
Phase 1 — Explore (auto-settle)
Look before asking. Every fact settled here removes a question from Phase 2:
git remote -v— GitHub remote? Which repo?gh repo view --json nameWithOwner,hasIssuesEnabledandgh auth statusconfirm theghpath works.command -v acli+acli jira auth status— is the Jira CLI installed and authenticated? Only offer Jira as a recommended answer when it is.gh label list— existing label vocabulary. If labels matching the five canonical triage roles (or close variants likebug:triage) already exist, capture them as the proposed mapping instead of proposing new labels.docs/agents/— prior output of this command? Ifissue-tracker.mdexists, this is an update run: show the current choice and ask whether to keep, tweak, or restart.CLAUDE.md/AGENTS.mdat the repo root — which exists, and does either already have an## Agent skillssection?CONTEXT.md,CONTEXT-MAP.md,docs/adr/— existing domain-doc layout.- Monorepo signals —
pnpm-workspace.yaml, aworkspacesfield,turbo.json, populatedpackages/*with their ownsrc/. Absence means single-context, which is almost every repo.
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 · 120 lines · 50 tokens per session scan A b76bf4705cfd
setup is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 5d ago), licensed MIT. It adds 50 tokens to every session and 2,019 once invoked, about $0.0003 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…