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/statusgit clone --depth 1 https://github.com/HigorAlves/orcWrote 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/commands/higoralves/orc/status)<a href="https://agentmods.dev/commands/higoralves/orc/status"><img src="https://agentmods.dev/badge/commands/higoralves/orc/status.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 | $0.00028 | $0.01289 |
| Opus 5 | $0.00014 | $0.00645 |
| Sonnet 5 | $0.00006 | $0.00258 |
| Haiku 4.5 | $0.00003 | $0.00129 |
Grade A, and why
status 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 3d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:status
Quick view of orc's workspace state. Useful when you've juggled multiple features and want to know what you've left half-done.
Arguments
--all— include completed and abandoned sessions (default: in-progress only).--branch <name>— filter to a specific branch.--repo <name>— workspace mode only: filter to one member repo (e.g.--repo api).
Workflow
Phase 1 — Detect context
The context banner is injected below — do not re-run detection:
!orc-workspace-detect --banner
orc context: repo— single-repo mode.orc context: workspace[…]— workspace mode.orc context: loose— outputCwd is neither a git repo nor a workspace parent — orc has no state to read here.and stop.
Phase 2 — Load registries
The registries are injected below — parse the sessions arrays straight from context instead of re-reading files (no-registry → output No orc workspaces yet — nothing to resume. and stop):
!orc-workspace-detect --registry
Workspace mode: the workspace registry comes first (sessions with scope: "workspace", repos, perRepoState, linkedPRs); each member repo's registry follows under a ### repo: <name> header:
- Sessions with
scope: "repo"(or noscope, treated as legacy) — standalone single-repo sessions inside a workspace child. Show in their own group. - Sessions with
scope: "workspace-member"— back-pointers to a workspace session already loaded above. Skip; do NOT double-render. --repo <name>filters workspace sessions'perRepoStaterows to that repo and filters the standalone-session group to that repo.--branch/--allfilters apply normally.
Phase 3 — Render
Render a markdown table. If a session has jiraTicket set, append a Jira column showing [<KEY>]; if no session in the table has one, omit the column entirely:
| # | Command | Branch | Phase | Status | Updated | Jira |
|---|-----------|------------------------------|-------|---------------|-------------|------------|
| 1 | plan | feat-142-notifs | 3/5 | in_progress | 2h ago | [JRA-123] |
| 2 | debug | fix-cache-stale | 2/7 | in_progress | yesterday | — |
| 3 | fan-out | refactor-billing | 4/6 | in_progress | 3 days ago | [PLAT-99] |
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.
- 3d ago First seen · 108 lines · 28 tokens per session scan A 1c4dbf88ff8d
status is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 7d ago), licensed MIT. It adds 28 tokens to every session and 1,289 once invoked, about $0.0001 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…