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/dwarvesf/dwarves-kit/wayfindgit clone --depth 1 https://github.com/dwarvesf/dwarves-kitWrote 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/dwarvesf/dwarves-kit/wayfind)<a href="https://agentmods.dev/commands/dwarvesf/dwarves-kit/wayfind"><img src="https://agentmods.dev/badge/commands/dwarvesf/dwarves-kit/wayfind.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.00071 | $0.02365 |
| Opus 5 | $0.00036 | $0.01182 |
| Sonnet 5 | $0.00014 | $0.00473 |
| Haiku 4.5 | $0.00007 | $0.00236 |
Grade A, and why
wayfind 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 today.
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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a wayfinder. A loose idea has arrived, too big for one session and wrapped in fog: the way from here to the destination is not visible yet. Your job is to find the way, not to charge at the destination: chart a shared map of decision tickets (questions whose resolution is a decision, not build slices), then resolve them one at a time until the way is clear.
Ported from mattpocock/skills wayfinder (MIT), re-based onto files + the kit board (SPEC-207; design: docs/research/2026-07-31-mattpocock-trio-adoption.md §1+§4). Tracker-native storage is deliberately NOT this command (parked; SPEC-207 Out of scope).
Router check first (upstream's admitted failure mode is over-reach). Wayfind is slower and denser than a single grill. A well-scoped feature belongs on /kit:grill + /kit:spec; a decomposable build with a clear route belongs on /kit:mega. Reach for wayfind only when the OPEN QUESTIONS outnumber the stateable ones.
Plan, don't do
Every 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 have reached the edge of the map: time to hand off. The map's ## Notes can override this per effort; absent that, produce decisions, not deliverables.
Where things live
_meta/megagoals/<slug>/
map.md # the map: the low-res index, loaded once per session
tickets/NN-<slug>.md # one decision ticket per file
ROADMAP.md # (later) the do-half; written at graduation, not by wayfind
Co-location is deliberate: wayfind is the decide-half of the folder whose do-half is the mega-goal ROADMAP (ADR-0032). Graduation happens in place. The board (SPEC-055) carries ONE umbrella row per map; tickets are NEVER duplicated as board rows.
map.md
The map is an index, not a store: a decision lives in exactly one place, its ticket file; the map only gists it and points. Open tickets are not listed in the body; they are found by scanning tickets/ (the frontier query below).
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.
- today First seen · 115 lines · 71 tokens per session scan A cdde79e8cb4b
wayfind is a command published in the GitHub repository dwarvesf/dwarves-kit (11 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 2,365 once invoked, about $0.0004 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-09-04.
Other commands, from other repositories
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Apply
Implement tasks from an OpenSpec change (Experimental).
OPSX: Archive
Archive a completed change in the experimental workflow.
OPSX: Bulk Archive
Archive multiple completed changes at once.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: New
Start a new change using the experimental artifact workflow (OPSX).