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 gaia-research/gaia-skill-heaven --skill wayfindergit clone --depth 1 https://github.com/gaia-research/gaia-skill-heavenWrote 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/gaia-research/gaia-skill-heaven/wayfinder)<a href="https://agentmods.dev/skills/gaia-research/gaia-skill-heaven/wayfinder"><img src="https://agentmods.dev/badge/skills/gaia-research/gaia-skill-heaven/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/gaia-research/gaia-skill-heaven/wayfinder"><img src="https://agentmods.dev/badge/skills/gaia-research/gaia-skill-heaven/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.00179 | $0.04075 |
| Opus 5.5 | $0.00072 | $0.01630 |
| Sonnet 5.5 | $0.00036 | $0.00815 |
| Haiku 4.5 | $0.00018 | $0.00407 |
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 1mo 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 — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wayfinder (Gaia)
This is the Gaia expression of Matt Pocock's wayfinder skill. Upstream is deliberately
tracker-agnostic: it says "the issue tracker should have been provided to you… consult
the tracker doc's 'Wayfinding operations' section for how THIS repo expresses them."
This file is that document. Upstream owns the method; this file pins down the mechanics — where maps live, how tickets are created and nested, how blocking is expressed, how the frontier is queried, how a ticket is claimed, how a resolution is recorded. Read the upstream SKILL.md for the method (mattpocock/skills → engineering/wayfinder); read this for how Gaia does it.
Wayfinder is cartography: planning an effort too big for one agent session as a map of decision tickets, worked one at a time until nothing is left to decide. It is not backlog hygiene and not issue resolution — see Not this skill.
1. Headquarters — one tracker, many repos
Every map and every ticket lives on the gaia-research/gaia-skill-tree issue tracker,
regardless of which repository the resulting code lands in. There is no second map
tracker, and a map is never split across repos.
export GAIA_HQ=gaia-research/gaia-skill-tree # headquarters — all wayfinder issues
Why: a map's whole value is that one issue holds the low-resolution view of an entire
effort. Efforts here routinely cross repo boundaries — a Skill Heaven benchmark decision
made in gaia-research changes door code in gaia-skill-heaven and registry vocabulary
in gaia-skill-tree. A map fragmented across three trackers is not a map.
Target-repo tagging
A ticket in HQ can point at work landing anywhere in the gaia-research org. Say where,
on the ticket body, as the first line:
**Target repo:** `gaia-research/gaia-skill-heaven`
Use a repo's full owner/name. Multiple targets are allowed (one line, comma-separated);
n/a is valid for a pure-decision ticket that lands no code anywhere. Minimum supported
scope is the big three:
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.
- 1mo ago First seen · 361 lines · 179 tokens per session scan A 4cc80b1e9270
wayfinder is a skill published in the GitHub repository gaia-research/gaia-skill-heaven (4 stars, last pushed today), licensed MIT. It adds 179 tokens to every session and 4,075 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
requirement-forge-refiner
Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution…
tasks
Turn an approved SPEC.md into a complete TASKS.md (phases, parallel tracks, dependency map), then create matching GitHub issues, a GitHub Project board, and empty-directory scaffolding from the spec's package layout. Use whenever the user invokes /ank:tasks, says "break this into tasks", "create the issues", "wire up…
agency-os
Notion-as-source-of-truth dispatch board. Status flow Suggestion→Discussion→To-Do→In Progress→Done with subtasks, recurring tasks, deps, batch agent execution. Trigger: 'suggest X', 'discuss X', 'approve', 'start X', 'run todo', 'mark X done', 'kill X', 'next', 'capture this to Notion', 'agency-os status'.
product-manager
Use when writing user stories or acceptance criteria, defining product requirements, prioritising a feature backlog, creating a product roadmap, analysing product metrics, facilitating discovery for a new feature, evaluating trade-offs between product directions, or any task that requires deciding what to build and…
project-manager
Use when planning sprints, tracking delivery milestones, managing dependencies, identifying risks, writing status reports, running retrospectives, or coordinating cross-functional execution of a defined scope. Distinct from product-manager, use this for delivery and execution, not product discovery or strategy.
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…