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 skills/danielvm-git/bigpowers/find-waynpx skills add danielvm-git/bigpowers --skill find-waygit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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.00055 | $0.01756 |
| Opus 5 | $0.00028 | $0.00878 |
| Sonnet 5 | $0.00011 | $0.00351 |
| Haiku 4.5 | $0.00006 | $0.00176 |
Grade A, and why
find-way 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 3d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Way
Concept
A large effort arrives — too big for one session, wrapped in fog. Find-way charts the way as a shared map on the repo's issue tracker, then works decision tickets — questions whose resolution is a decision, not build slices — one at a time until the route is clear.
Plan, don't do. Each ticket resolves a decision. The map is done when the way is clear — nothing left to decide before someone executes.
Refer by name. Every map and ticket is an issue with a title. Always use the name, never bare ids or numbers.
The Map
A single issue labelled wayfinder:map — the canonical artifact. Child issues are its tickets.
## Destination
<what reaching the end looks like — one or two lines>
## Notes
<domain, skills to consult, standing preferences>
## Decisions so far
- [closed ticket title](link) — one-line gist
## Not yet specified
<in-scope fog you can't ticket yet>
## Out of scope
<work ruled beyond the destination>
Ticket Types
| Type | Label | Mode | Purpose |
|---|---|---|---|
| Research | wayfinder:research |
AFK | Surface facts from docs/APIs |
| Prototype | wayfinder:prototype |
HITL | Cheap artifact to react to |
| Grilling | wayfinder:grilling |
HITL | One-question-at-a-time dialogue |
| Task | wayfinder:task |
Either | Manual work unblocking a decision |
HITL = human in the loop. AFK = agent alone.
Two Modes
Chart the Map
User invokes with a loose idea.
- Name the destination — grill to pin down what this map finds its way to
- Map the frontier — breadth-first: surface open decisions and first steps. If no fog emerges, the effort fits one session — skip the map
- Create the map issue (label
wayfinder:map) - Create tickets as child issues, then wire blocking edges in a second pass
- Fire research subagents for each
researchticket in parallel - Stop — charting resolves nothing
Work Through the Map
User invokes with a map (URL/number). Ticket optional — without one, pick the next frontier ticket.
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.
- 3d ago First seen · 192 lines · 55 tokens per session scan A 3e25fff1479a
find-way is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 26d ago), licensed MIT. It adds 55 tokens to every session and 1,756 once invoked, about $0.0003 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
pm/competitive-analysis
竞品调研和分析方法，通过系统性分析竞品的功能、体验和策略，发现差异化机会.
macrothink
User-invoked read-only pass for checking whether the current direction is tunnel-visioned: strip the session's bait, fan out 2 to 5 same-model fresh reads, and report divergence first without treating convergence as proof.
nba
Read the live cycle state and return the single highest-leverage next best action, not a menu. Use when a project is between phases, the author asks what to do next, too many valid threads are open, or the work needs re-entry into frame, build, drive, re0-memo, hate, re0-work, or ship.
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-domain-research
Conduct domain and industry research. Use when the user says "lets create a research report on [domain or industry]".
harness-engineering
Use when an agent workflow needs production-like runtime controls for context, tools, permissions, observability, scheduling, evaluation, recovery, or maintenance.