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 skills add xbklairith/kisune --skill wayfindergit clone --depth 1 https://github.com/xbklairith/kisuneWrote 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/skills/xbklairith/kisune/wayfinder)<a href="https://agentmods.dev/skills/xbklairith/kisune/wayfinder"><img src="https://agentmods.dev/badge/skills/xbklairith/kisune/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/skills/xbklairith/kisune/wayfinder"><img src="https://agentmods.dev/badge/skills/xbklairith/kisune/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.00090 | $0.01624 |
| Opus 5.5 | $0.00036 | $0.00650 |
| Sonnet 5.5 | $0.00018 | $0.00325 |
| Haiku 4.5 | $0.00009 | $0.00162 |
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 11d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wayfinder
Overview
A loose idea, too big for one session, wrapped in fog: the way from here to the destination is not visible yet. Wayfinding finds that way instead of charging at the destination. It keeps a map of decision tickets (questions whose answer is a decision or a fact a decision waits on) and resolves them one per session until nothing is left to decide.
Plan, don't do. A ticket produces a decision, not a deliverable. The pull to start building is the signal that you have reached the edge of the map: hand off to spec-driven-planning (or spec-driven-implementation) with the decisions as input. An effort can override this in its map's Notes.
Don't chart what you can't see. A full phase-by-phase task list for a multi-month effort, written before the first question is answered, is a guess dressed as a plan. Ticket only questions you can state sharply now; leave the rest as fog.
When to Use
- The work spans more sessions than one context can hold, and key decisions are still open
- The user says they don't know where to start on something large
- A session should resume a map: "continue the migration plan", "what's next on "
Not for work one session can plan: if charting surfaces no fog, say so and use spec-driven-planning directly.
The map on disk
docx/wayfinder/<effort>/
├── map.md
└── tickets/
├── 01-<slug>.md
└── 02-<slug>.md
map.md is an index, not a store. It is read once per session; ticket detail lives only in the ticket.
# <Effort name>
## Destination
<What reaching the end looks like: a spec to hand off, a locked decision, a change made. One or two lines.>
## Notes
<Domain, constraints, skills every session should load, standing preferences.>
## Decisions so far
- [<ticket title>](tickets/03-<slug>.md): <one-line gist of the answer>
## Not yet specified
<In-scope fog: questions you can see coming but can't phrase sharply yet. Loose prose.>
## Out of scope
- <gist> — <why>, see [<ticket title>](tickets/NN-<slug>.md) if one was closed for it
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 125 lines · 90 tokens per session scan A 612f03cba48a
wayfinder is a skill published in the GitHub repository xbklairith/kisune (3 stars, last pushed 8d ago), licensed MIT. It adds 90 tokens to every session and 1,624 once invoked, about $0.0004 per session on Opus 5.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-10-07.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.