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/startgit 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.00043 | $0.02052 |
| Opus 5 | $0.00022 | $0.01026 |
| Sonnet 5 | $0.00009 | $0.00410 |
| Haiku 4.5 | $0.00004 | $0.00205 |
Grade A, and why
start 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:start
Kick off a new feature with isolation, a written plan, and the first failing test — all before production code is touched. The TDD red light is the entry gate.
Arguments
-
--auto[=guided|full]— autopilot level for this run (overridesinteraction_policy; taxonomy inorc:using-orc). Soft-inward gates consult the resolved policy —guidedauto-advances mechanical confirms with a printed one-liner;fullpre-approves them from settled decisions (orc:state-protocol), stopping only on escalation-only conditions. Hard-outward gates are unaffected at every level. -
--worktree <path>— optional explicit worktree directory. If omitted, the worktree skill picks one safely. -
--jira <KEY>— optional. Link a Jira ticket key (e.g.JRA-123) to this session. Two effects: (1) Phase 1 fetches the ticket summary viaacli jira workitem view <KEY> --fields "summary" --json, slugifies it, and offersfeat/<KEY>-<slug>as the suggested branch name toorc:using-git-worktrees; (2) the flag is forwarded to/orc:planin Phase 2, suppressing the Phase 1 link prompt and writingjiraTicket: <KEY>into the session's.orc/state. Validate against^[A-Z][A-Z0-9_]*-\d+$.
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).
In workspace mode, resolve targetRepos from --repos/--repo/--all-repos/--this-repo or via AskUserQuestion. Iron rule: no silent broadcast.
Phase 1 — Worktree(s)
Invoke orc:using-git-worktrees. Create an isolated worktree off the current default branch (typically main). Switch the session to that worktree. The PreToolUse hook will refuse subsequent commits to main/master/develop, so you must be on a feature branch from this point.
If --jira <KEY> was passed: invoke orc:jira-cli and run acli jira workitem view "$KEY" --fields "summary" --json | jq -r '.fields.summary'. Slugify (lowercase, replace non-[a-z0-9-] with -, collapse repeats, trim leading/trailing -). Suggest feat/<KEY>-<slug> as the branch name to orc:using-git-worktrees. The user can accept or override.
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 · 128 lines · 43 tokens per session scan A 470e867ac21b
start is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 6d ago), licensed MIT. It adds 43 tokens to every session and 2,052 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
test
Run Postman collection tests, analyze results, diagnose failures, and suggest fixes.
deploy-flow
Deploy a Postman Flow so it becomes triggerable, proposing and confirming a trigger path.
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…
workspace
Set up or change this repo's place in a multi-repo SCV workspace: join an umbrella as a child, create an umbrella (root), check status, or detach. Friendly — no long flags to remember. Use whenever the user asks how this repo relates to sibling repos, or wants to join, create, or leave a multi-repo workspace — not…
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.
analyze-dependabot
分析 Dependabot 安全告警并创建安全分析文档.