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/adrgit 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/adr)<a href="https://agentmods.dev/commands/higoralves/orc/adr"><img src="https://agentmods.dev/badge/commands/higoralves/orc/adr.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.00825 |
| Opus 5 | $0.00021 | $0.00413 |
| Sonnet 5 | $0.00008 | $0.00165 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
adr 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:adr
Author a new ADR (or update an existing one's status) following orc:adr-writing.
Arguments
<title>— optional. Short noun phrase describing the decision (e.g. "use Postgres for primary store"). If omitted, prompts viaAskUserQuestion.--supersede NNNN— optional. Marks an existing ADR as superseded and authors a new one whoseContextcites the predecessor.
Workflow
Phase 1 — Confirm an ADR is warranted
Invoke orc:adr-writing. Apply its "all of these are true" test:
- architectural (multi-module / boundary / convention)
- non-obvious (real alternatives exist)
- durable (≥ 3 months expected lifetime)
If borderline, print the Gate headline (**⛔ Gate — is this ADR-worthy?**, one line on which criterion is borderline, per orc:callouts), then AskUserQuestion:
- "Yes, write the ADR"
- "Smaller — propose a single-paragraph design note in the relevant code instead"
- "Skip — this isn't really an architectural decision"
Phase 2 — Locate docs/adr/
If the directory doesn't exist, create it and add a one-line docs/adr/README.md linking to the convention. Find the next sequence:
ls docs/adr 2>/dev/null | grep -E '^[0-9]{4}-' | sort | tail -1
Increment to get the new four-digit sequence (0001 if first).
Phase 3 — Draft
Author docs/adr/NNNN-<kebab-title>.md using the template from orc:adr-writing. Fill every section with real content. Don't leave TBD or placeholder text — delete sections that genuinely have no content.
If --supersede NNNN was passed:
- Read
docs/adr/NNNN-*.md. Update its status toSuperseded by <new-NNNN>and bump its date. - The new ADR's
ContextMUST cite the predecessor and explain why the situation changed.
Phase 4 — Review
Print the Gate headline (**⛔ Gate — ADR review**), show the draft, then AskUserQuestion:
- "Looks good — commit"
- "Edit before commit" (loop back to Phase 3)
- "Save as draft (Status: Proposed)" — commits with status flag flipped
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 · 81 lines · 42 tokens per session scan A fc0d11558527
adr is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 7d ago), licensed MIT. It adds 42 tokens to every session and 825 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…