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 darellchua2/opencode-config-template --skill wayfinder-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/darellchua2/opencode-config-template/wayfinder-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/wayfinder-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/wayfinder-skill/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/darellchua2/opencode-config-template/wayfinder-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/wayfinder-skill.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.00058 | $0.02071 |
| Opus 5.5 | $0.00023 | $0.00828 |
| Sonnet 5.5 | $0.00012 | $0.00414 |
| Haiku 4.5 | $0.00006 | $0.00207 |
Grade A, and why
wayfinder-skill 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adapted from mattpocock/skills
skills/engineering/wayfinder (MIT) for OpenCode — dependencies mapped to
local skills/subagents, tracker handling per house MCP policy.
A loose idea has arrived, too big for one agent session, wrapped in fog: the way from here to the destination isn't visible yet. Wayfinding finds that way instead of charging at the destination. This skill 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 build slices) one at a time until the route is clear.
The destination varies per effort, and naming it is the first act of charting: a spec to hand off, a decision to lock before planning, or a change made in place. The map is domain-agnostic.
Plan, don't do
Wayfinder is planning by default: each ticket resolves a decision, and
the map is done when nothing is left to decide before someone does the thing.
The pull to just do the work is usually the signal you've reached the edge of
the map — hand off (e.g. to ticket-creation-skill for execution tickets,
then /run-worktree-pipeline to execute). An effort can override this in its
Notes, carrying execution into the map itself.
Refer by name
Every map and ticket is an issue, so it has a name: its title. In everything the human reads, refer to it by name, never a bare number. The id and URL ride inside the name link, never stand in for it.
The Map
The map is a single issue labelled wayfinder:map — the canonical artifact.
Its tickets are child issues. The map is an index, not a store: a
decision lives in exactly one place (its ticket); the map gists and links.
Map body
## Destination
<what reaching the end looks like — one or two lines; every session orients to it first>
## Notes
<domain; skills each session should consult; standing preferences>
## Decisions so far
- [<closed ticket title>](link): <one-line gist of the answer>
## Not yet specified
<fog: in-scope questions you can't phrase sharply enough to ticket yet>
## Out of scope
<work ruled beyond the destination; closed, never graduates>
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 Changed 3dbe3548c77a
- 1mo ago First seen · 194 lines · 58 tokens per session scan A 18659ad384ff
wayfinder-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 28d ago), licensed Apache-2.0. It adds 58 tokens to every session and 2,071 once invoked, about $0.0002 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-10.
Other skills, from other repositories
git-ship
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.