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 aethrox/doctrine --skill wayfindergit clone --depth 1 https://github.com/aethrox/doctrineWrote 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/aethrox/doctrine/wayfinder)<a href="https://agentmods.dev/skills/aethrox/doctrine/wayfinder"><img src="https://agentmods.dev/badge/skills/aethrox/doctrine/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/aethrox/doctrine/wayfinder"><img src="https://agentmods.dev/badge/skills/aethrox/doctrine/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.00073 | $0.01082 |
| Opus 5 | $0.00036 | $0.00541 |
| Sonnet 5 | $0.00015 | $0.00216 |
| Haiku 4.5 | $0.00007 | $0.00108 |
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 10d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wayfinder
Some work isn't unclear because nobody's thought about it; it's unclear because it depends on decisions that haven't been made yet, and those decisions depend on others. This skill's defining constraint, from the RFC process IETF and Rust use for exactly this problem, is to chart large, uncertain work as a sequence of individually-written decisions, each one settled and recorded before the next is opened, rather than one big document trying to resolve everything at once.
Once the path is clear (no open decisions block the destination anymore), hand off to spec-to-tickets for execution. Wayfinder's job ends where a spec's job begins.
Phase 1: Name the destination
Before charting anything, state what reaching the end of this effort looks like: a spec ready to hand off, a design decision locked in, or a migration completed. One or two lines, fixed before anything else, because it's what decides which open questions are actually in scope and which aren't. A destination that shifts mid-effort invalidates decisions already made against the old one; if it must shift, say so explicitly and re-check standing decisions against the new destination rather than silently continuing.
Phase 2: Chart the open decisions
Fan out breadth-first across the whole space (every open question standing between here and the destination) rather than diving deep on the first one found. For each:
- State the decision precisely enough that "resolved" and "not yet resolved" are unambiguous.
- Note what it blocks and what blocks it. A decision that depends on another isn't ready to open yet.
- If a genuine open area exists but can't be phrased as a precise question yet, leave it as unspecified rather than forcing it into a premature decision; a vague decision produces a vague, unusable answer.
If this pass surfaces no real open questions (the path to the destination is already obvious), stop here. The work doesn't need staging; it needs a spec.
Phase 3: Resolve one decision at a time
What ships with it
1 file 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.
- 10d ago First seen · 62 lines · 73 tokens per session scan A e67e25456aa3
wayfinder is a skill published in the GitHub repository aethrox/doctrine (18 stars, last pushed 28d ago), licensed MIT. It adds 73 tokens to every session and 1,082 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-08-30.
Other skills, from other repositories
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — Diagnostics issues first, then errors, failed tool calls, latency, regressions, and low online-eval scores. With the Opik MCP connected it lists the project's agentinsightsissue entities, then fills the gaps with list (filters, sort, a time…
qa-knowledge
To run QA engineering — requirements/gap analysis, scenario & spec design, test implementation, failure triage — over the QA knowledge base.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.