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 RobinNorberg/oh-my-copilot --skill ask-navigatorgit clone --depth 1 https://github.com/RobinNorberg/oh-my-copilotWrote 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/robinnorberg/oh-my-copilot/ask-navigator)<a href="https://agentmods.dev/skills/robinnorberg/oh-my-copilot/ask-navigator"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/ask-navigator/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/robinnorberg/oh-my-copilot/ask-navigator"><img src="https://agentmods.dev/badge/skills/robinnorberg/oh-my-copilot/ask-navigator.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.00078 | $0.04101 |
| Opus 5.5 | $0.00031 | $0.01640 |
| Sonnet 5.5 | $0.00016 | $0.00820 |
| Haiku 4.5 | $0.00008 | $0.00410 |
Grade A, and why
ask-navigator 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 16d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ask Navigator
Ask-navigator is the shipyard's navigator: it takes an effort wrapped in fog — the way from here to the destination isn't visible yet — and charts it as a map of decision tickets on the repo's issue tracker, then works the frontier one ticket per session until the route is clear. It produces decisions, never deliverables: when the way is clear it hands off, it doesn't build. Delivery belongs to /oh-my-copilot:launch.
The role contract. The captain (the human) signs the destination (W1) and the chart (W2); the navigator drafts everything else and never answers a question that belongs to the captain — a grilling session in which the agent answers its own questions has broken the role, not just the process. Facts are the navigator's job; decisions are the captain's.
Fog test. An effort has fog when either answer is no:
- Q1 — Can the destination be stated in one sentence: the spec, decision, or change this effort is finding its way to?
- Q2 — Can the first three decisions be stated precisely right now, even though none of them can be answered yet?
Both yes → no map is needed; run /oh-my-copilot:launch (its fog gate sends efforts here only when an answer is no). Either no → chart first. ask-navigator is also reachable directly: invoke it with a loose idea, with residual questions handed over by launch's fog gate, or with no argument to continue the open map.
Map home
The map is a single issue labelled navigator:map on the repo's issue tracker; its decision tickets are child issues of the map. The tracker should have been recorded by /oh-my-copilot:drydock; if none was recorded, ask once and remember the answer inside the map's Notes.
The tracker is the only map medium — there is no local fallback: one map issue, child issues per ticket, native blocking/sub-issue relationships. Concurrent sessions and the tracker's own UI render the frontier — the map lives where humans already look. A map written to local files strands decisions where later sessions, the captain, and launch will never find them; do not fall back to local files. If the tracker is unreachable, stop and report the blocker. Create the navigator:map label if the tracker doesn't have it yet; ticket types live in the ticket body, not in labels.
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.
- 16d ago Changed · +7 lines 3e0196c7032d
- 25d ago Changed · +16 lines · +78 tokens per session bdb9c0bcc99a
- 1mo ago First seen · 128 lines · 0 tokens per session scan A f82ec0ab39e2
ask-navigator is a skill published in the GitHub repository RobinNorberg/oh-my-copilot (5 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 4,101 once invoked, about $0.0003 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-08.
Other skills, from other repositories
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…
prepare-ticket
Use when asked whether a ticket or issue is ready for development, or to prepare, validate, refine, challenge, or sanity-check a Jira work item, GitHub Issue, or GitLab Issue before building it. Checks material claims against evidence, follows questions until outcome decisions are settled, rewrites the title and…
implement-ticket
Use when asked to implement, build, or pick up a ticket end to end — a Jira work item, GitHub Issue, or GitLab Issue — including "implement ABC-123", "implement gh issue #137", "work on issue 137", or "pick up this ticket". Critiques the request against the code, builds it in a throwaway git worktree, verifies it with…
estimate-size
Estimate software tickets and work items with a configurable relative-sizing workflow. Respect dedicated estimators and local project rules, and use the built-in defaults when no local rules are provided.
fetch-ticket
Reusable ticket reader that resolves a Jira work item, GitHub Issue, or GitLab Issue through the project's saved route and returns it as one provider-neutral ticket with every comment verbatim. Invoked by prepare-ticket and implement-ticket; not for validating or implementing a ticket directly, use those skills…
write-prd
Create a PRD and user stories through user interview, codebase exploration, and component design. Use when user wants to write a PRD, create a product requirements document, user stories or plan a new feature.