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/rfcgit 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/rfc)<a href="https://agentmods.dev/commands/higoralves/orc/rfc"><img src="https://agentmods.dev/badge/commands/higoralves/orc/rfc.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.00042 | $0.01156 |
| Opus 5 | $0.00021 | $0.00578 |
| Sonnet 5 | $0.00008 | $0.00231 |
| Haiku 4.5 | $0.00004 | $0.00116 |
Grade A, and why
rfc 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 4d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:rfc
Author a Request for Comments (RFC) before committing to an implementation.
Arguments
<title>— optional. One-line problem statement (will be polished into a noun phrase). Prompts if omitted.--grill— after drafting, invokeorc:grill-meto stress-test the design.--review <path>— review an existing RFC instead of authoring a new one. Walks the doc with critique focused on missing alternatives, undefined success criteria, hidden assumptions.
Workflow
Phase 1 — Gate (when authoring)
Invoke orc:rfc-writing. Apply its "any of these are true" test:
- multi-team / multi-service touchpoints
- ≥ 2 weeks of engineering effort
- locks in technology, protocol, or interface
- you're genuinely unsure between alternatives
If none are true, print the Gate headline (**⛔ Gate — is this RFC-worthy?**, per orc:callouts), then AskUserQuestion:
- "Smaller scope — use
/orc:planinstead (assumes design is settled)" - "Even smaller — use
/orc:adr(recording a decision already made)" - "Override — proceed with the RFC anyway"
Phase 2 — Initialize workspace
Determine the current branch (sanitize). Create .orc/<sanitized-branch>/files/ if absent. Locate docs/rfcs/ (create if absent, add docs/rfcs/README.md linking to the convention). Find the next sequence number.
Register state: orc-state init --command rfc --total-phases 5 (6 with --grill), then orc-state phase set 2. Defer to orc:state-protocol for schema and rules.
Phase 3 — Draft Goals + Non-goals first
These two sections bound everything that follows. Use AskUserQuestion to walk them:
- "What MUST this proposal accomplish?" (goals)
- "What is explicitly out of scope?" (non-goals)
Save the partial draft to .orc/<branch>/files/rfc-NNNN.md. Bump checkpoint to phase=3.
Phase 4 — Draft remaining sections
Following the template from orc:rfc-writing, fill: Background, Proposed design (with subsections: high-level shape, key interfaces, failure modes, migration), Alternatives considered, Open questions, Risks, Success criteria.
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.
- 4d ago First seen · 102 lines · 42 tokens per session scan A 66f43d29348a
rfc is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 8d ago), licensed MIT. It adds 42 tokens to every session and 1,156 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…