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.
git 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/wayfinder)<a href="https://agentmods.dev/commands/higoralves/orc/wayfinder"><img src="https://agentmods.dev/badge/commands/higoralves/orc/wayfinder/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/higoralves/orc/wayfinder"><img src="https://agentmods.dev/badge/commands/higoralves/orc/wayfinder.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00063 | $0.02279 |
| Opus 5 | $0.00032 | $0.01140 |
| Sonnet 5 | $0.00013 | $0.00456 |
| Haiku 4.5 | $0.00006 | $0.00228 |
Grade A, and why
wayfinder 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 8d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/orc:wayfinder
A loose idea has arrived — too big for one agent session, and wrapped in fog: the way from here to the destination isn't visible yet. Wayfinding is about finding that way, not charging at the destination. This command charts the way as a shared map on the repo's issue tracker, then works its decision tickets — questions whose resolution is a decision, not slices of a build to execute — one per session until the route is clear.
Where this sits
/orc:plan— the work fits one session: draft a TDD-shaped plan now./orc:wayfinder— the work spans many sessions and the open questions are decisions: chart them, resolve one at a time.orc:to-issues— the deciding is done: slice the settled plan into tracer-bullet implementation issues.
A finished map typically hands off to /orc:plan or orc:to-issues — the destination is often exactly the spec they consume.
Phase 0 — Read the tracker layer
Run the orc:tracker-config read protocol, then consult issue-tracker.md's "Wayfinding operations" section — where the map, child tickets, blocking edges, frontier query, claim, and resolve physically live is tracker-specific (GitHub sub-issues + native dependencies; Jira links via acli; local markdown files). The skill owns the missing-config gate (one canonical ask; a defaults answer is a settled decision for the session).
Principles
Plan, don't do. Each ticket resolves a decision; the map is done when nothing is left to decide before someone goes and does the thing. The pull to just do the work is usually the signal you've reached the edge of the map and it's time to hand off. An effort can override this in its map Notes — absent that, produce decisions, not deliverables.
Refer by name. Every map and ticket has a name — its title. In everything the human reads, refer to it by name with the link riding inside ([Pick the session store](url)), never a bare #42. A wall of numbers is illegible.
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.
- 8d ago First seen · 139 lines · 63 tokens per session scan A 61dc08d16425
wayfinder is a command published in the GitHub repository HigorAlves/orc (6 stars, last pushed 12d ago), licensed MIT. It adds 63 tokens to every session and 2,279 once invoked, about $0.0003 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
interview
Interview & refine a spec, task, or spec file in-depth.
make-pr
Render a cognitive-aid PR body from flow-next state and open via gh.
pilot
Single-tick autonomous build-loop conductor (one item, one stage per invocation; pipeline.chainStages==on chains make-pr after a fresh qa verdict); --backlog/--auto widens it to triage the whole open backlog.
tracker-sync
Project a flow spec to a tracker (Linear/GitHub/GitLab/Jira) and reconcile body/status/comments two-way — projection, not coordination. NOT plan-sync (/flow-next:sync).
audit
Audit .flow/memory/ entries against the current codebase — Keep / Update / Consolidate / Replace / Delete / Harden per entry.
features
Seed or maintain the committed user-POV feature map at .flow/features/.