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-skill-creatorgit 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-skill-creator)<a href="https://agentmods.dev/skills/qf-studio/navigator/nav-skill-creator"><img src="https://agentmods.dev/badge/skills/qf-studio/navigator/nav-skill-creator/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-skill-creator"><img src="https://agentmods.dev/badge/skills/qf-studio/navigator/nav-skill-creator.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.00053 | $0.03022 |
| Opus 5.5 | $0.00021 | $0.01209 |
| Sonnet 5.5 | $0.00011 | $0.00604 |
| Haiku 4.5 | $0.00005 | $0.00302 |
Grade A, and why
nav-skill-creator 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 11d 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-skill-creator — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navigator Skill Creator
Create project-specific skills by analyzing codebase patterns and automating repetitive workflows.
When to Invoke
Auto-invoke when user mentions:
- "Create a skill for [pattern]"
- "Automate this workflow"
- "We keep doing X manually"
- "Enforce this pattern"
- "Generate boilerplate for [feature type]"
- "We need consistency for [task type]"
What This Does
- Analyzes codebase to understand project patterns
- Identifies best practices from existing code
- Generates skill with:
- Auto-invocation triggers
- Predefined functions
- Templates
- Examples
- Tests the generated skill
- Documents the new skill
Execution Steps
Step 1: Understand Skill Request
Ask clarifying questions:
- What pattern/workflow to automate?
- What triggers should invoke this skill?
- What output format is expected?
- Are there existing examples in the codebase?
Example dialogue:
User: "Create a skill for adding React components"
Assistant: "I'll analyze your codebase to understand React component patterns.
- What directory are components in?
- Do you use TypeScript or JavaScript?
- Do you want tests generated automatically?
- Are there style files (CSS/SCSS) per component?"
Step 2: Analyze Codebase Patterns
Use Task agent to explore (saves 60-80% tokens):
Use Task agent with subagent_type=Explore:
"Find existing [pattern type] in codebase:
- Locate all [files matching pattern]
- Identify common structure
- Extract best practices
- Find configuration files
- Return summary of findings"
What to look for:
- File naming conventions (kebab-case, PascalCase, etc.)
- Directory structure patterns
- Import/export patterns
- Testing patterns
- Configuration patterns
- Documentation patterns
Example for React components:
Task agent finds:
- Components in src/components/
- PascalCase naming (UserProfile.tsx)
- Co-located tests (UserProfile.test.tsx)
- Props interfaces defined above component
- Export default at bottom
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago Changed 8c1944a635f5
- 21d ago First seen · 532 lines · 53 tokens per session scan A c15fb1a881c2
nav-skill-creator is a skill published in the GitHub repository qf-studio/navigator (355 stars, last pushed yesterday), licensed MIT. It adds 53 tokens to every session and 3,022 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
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.
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.
product-design
Automates design review, token extraction, component mapping, and implementation planning. Reduces design handoff from 6-10 hours to 5 minutes via direct Figma MCP integration. Auto-invoke when user mentions design review, Figma mockup, or design handoff.
social-media-post
Generate optimized social media posts for Threads, X (Twitter), and LinkedIn. Analyzes platform algorithms, applies best practices, and creates engaging content tailored to each platform. Local skill for Navigator marketing only.
nav-loop
Run tasks until complete with structured completion signals. Auto-invoke when user says "run until done", "keep going until complete", "iterate until finished", "loop mode", "autonomous mode".
nav-skill-creator
Analyze codebase patterns and create custom skills for repetitive workflows. Use when project needs automation or pattern enforcement. Auto-invoke when user says "create a skill for...", "automate this workflow", or "we keep doing X manually".