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/prdgit 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.01243 |
| Opus 5 | $0.00022 | $0.00622 |
| Sonnet 5 | $0.00009 | $0.00249 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
prd 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:prd
Author a new PRD following orc:prd-writing. Lives at docs/prds/NNNN-<kebab-title>.md.
Arguments
<title>— optional. Short noun phrase describing the feature (e.g. "report CSV export"). If omitted, prompts viaAskUserQuestion.--interview— optional. Walk the user through the seven-question PRD interview (Problem, Audience, Success metric, In/Out scope, Open questions, Dependencies) before drafting. Default is to draft from existing context only.--from-jira <KEY>— optional. Pre-seed the PRD'sProblem,Linked tickets, and (if available)Audiencesections from a Jira ticket viaorc:jira-cli.
Workflow
Phase 1 — Confirm a PRD is warranted
Invoke orc:prd-writing. Apply its "all of these are true" test:
- user-facing outcome
- non-obvious intent (real product question)
- non-trivial work (multi-day or coordinated)
If borderline, print the Gate headline (**⛔ Gate — is this PRD-worthy?**, per orc:callouts), then AskUserQuestion:
- "Yes, write the PRD"
- "Smaller — issue or design note instead"
- "Skip — this is implementation-only; reach for a plan"
- "Refocus — this is technical contract, write a TRD with
/orc:trd"
Phase 2 — Locate docs/prds/
If the directory doesn't exist, create it and add a one-line docs/prds/README.md linking to orc:prd-writing. Find the next sequence:
ls docs/prds 2>/dev/null | grep -E '^[0-9]{4}-' | sort | tail -1
Increment to get the new four-digit sequence (0001 if first).
Phase 3 — Gather inputs
If --from-jira <KEY> was passed, fetch the ticket:
acli jira workitem view "$KEY" --fields "key,summary,description,assignee,priority,status,labels" --json
Use the response to seed:
Problem(fromsummary+description)Linked tickets(the key itself)Audience(if labels indicate persona — heuristic; user confirms)
If --interview was passed, walk the seven-question interview from orc:prd-writing (skip questions answered by --from-jira or by conversation context). Batch into 2–3 AskUserQuestion calls; don't drip one at a time.
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 · 109 lines · 43 tokens per session scan A 6ba99c209eb6
prd 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 1,243 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 安全告警并创建安全分析文档.