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 qf-studio/navigator --skill nav-pilotgit clone --depth 1 https://github.com/qf-studio/navigatorWrote 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/qf-studio/navigator/nav-pilot)<a href="https://agentmods.dev/skills/qf-studio/navigator/nav-pilot"><img src="https://agentmods.dev/badge/skills/qf-studio/navigator/nav-pilot/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/qf-studio/navigator/nav-pilot"><img src="https://agentmods.dev/badge/skills/qf-studio/navigator/nav-pilot.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.00062 | $0.01349 |
| Opus 5.5 | $0.00025 | $0.00540 |
| Sonnet 5.5 | $0.00012 | $0.00270 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
nav-pilot 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 21d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- nav-pilot — 100% identical, 0 lines differ
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.
Navigator → Pilot Dispatch Skill
Hand a finished Navigator task doc off to Pilot by creating the pilot-labeled
GitHub issue Pilot polls, then record the issue back into the doc.
This skill does NOT validate the doc. Spec checking is Pilot's job (its
spec_validator). nav-pilot only resolves the doc, creates the labeled issue,
and records the result. It consumes what nav-task authored — it does not
author or archive docs itself.
When to Invoke
Invoke when the user says:
- "Dispatch TASK-XX to Pilot"
- "Hand this off to Pilot" / "send to Pilot"
- "Queue TASK-XX for Pilot" / "create the Pilot issue"
DO NOT invoke when:
- User is authoring/archiving a task doc (that's
nav-task) - User wants Pilot worker status (out of scope — this skill is one-way)
- No task doc exists yet (tell them to create one with
nav-taskfirst)
Execution Steps
Step 1: Resolve the Target Task Doc
- Explicit ID ("TASK-07"): use
.agent/tasks/TASK-07-*.md. - No ID: pick the active/in-progress task. If ambiguous, list candidates
(
ls .agent/tasks/*.md) and ask which one. - If the file does not exist, stop and tell the user to author it first.
Read the doc and extract:
- Title = the first H1 (
# TASK-XX: <name>), stripped of theTASK-XX:prefix if present (or keep the full H1 — match what Pilot expects). - Body file path = the doc itself (passed via
--body-file, never inlined).
Step 2: Load Pilot Config
Read pilot from .agent/.nav-config.json:
"pilot": {
"enabled": true,
"label": "pilot",
"repo": null
}
label(default"pilot"): the label Pilot polls for.repo(defaultnull): targetowner/name. Whennull,ghuses the current git repository's origin — do NOT pass--repo.
If pilot.enabled is false, stop and tell the user to enable it.
Step 3: Build the Command
gh issue create \
--title "<H1 title>" \
--label "<pilot.label>" \
--body-file ".agent/tasks/TASK-XX-<slug>.md" \
[--repo "<pilot.repo>"] # only when pilot.repo is set
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.
- 21d ago First seen · 151 lines · 62 tokens per session scan A 75569194a604
nav-pilot is a skill published in the GitHub repository qf-studio/navigator (355 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 1,349 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-25.
Other skills, from other repositories
github-issues
Manage GitHub issues, pull requests, CI runs, and repository operations via the gh CLI.
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
nav-install-multi-claude
DEPRECATED. The multi-Claude orchestration scripts are deprecated in favor of native Claude Code Workflows; no installation is needed. Auto-invokes on "install multi-Claude workflows", "set up multi-Claude", "enable parallel execution" to explain the deprecation.
github-project-management
GitHub project management with issue tracking, project-board automation, and sprint planning. Use when triaging or organizing issues, automating a project board, planning a sprint, or running release/roadmap coordination on GitHub.
nav-multi
DEPRECATED. Multi-Claude shell orchestration is superseded by native Claude Code Workflows. Auto-invokes on "run multi-agent workflow", "parallel agents for", "multi-claude for", "spawn agents for" to redirect the user to the native Workflow and Agent tools.
wrap-up
End-of-session handler: checks if the plan is complete. If complete: quick retrospective, forward follow-up prompt, and (in a repo) refresh + clean gone branches. If incomplete: skip cleanup, emit resume prompts. Cleanup needs a repo; rest doesn't.