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 agents/fomo-driven-development/strategic-claude-base/codex-navigator.templategit clone --depth 1 https://github.com/Fomo-Driven-Development/strategic-claude-baseWrote 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/agents/fomo-driven-development/strategic-claude-base/codex-navigator.template)<a href="https://agentmods.dev/agents/fomo-driven-development/strategic-claude-base/codex-navigator.template"><img src="https://agentmods.dev/badge/agents/fomo-driven-development/strategic-claude-base/codex-navigator.template.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01299 |
| Opus 5 | $0.00000 | $0.00649 |
| Sonnet 5 | $0.00000 | $0.00260 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
codex-navigator.template 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 4d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navigator Guidance: [Task/Feature Name]
Session Context
Driver Focus: [file:line] - [Current implementation area]
Current Goal: [What the driver is trying to accomplish]
Session Phase: [Analysis | Implementation | Review | Refactoring]
Strategic Assessment
Current State Analysis
- Progress: [What has been accomplished so far]
- Architecture: [Relevant patterns and design decisions observed]
- Dependencies: [Key components or files involved]
Approach Recommendation
Suggested Path: [High-level strategy recommendation]
Reasoning: [Why this approach is recommended based on architecture, patterns, performance, etc.]
Alternative Considerations: [Other approaches and why current is preferred]
Navigation Guidance
Immediate Next Steps
-
[Step 1] - [Clear action with reasoning]
- Location:
[file:line]- [Where to focus] - Pattern: [Reference to similar implementation if applicable]
- Goal: [What this step accomplishes]
- Location:
-
[Step 2] - [Next logical action]
- Context: [Why this follows from step 1]
- Reference:
[file:line]- [Example or utility to use]
Code Location References
- Current Focus:
[current-file:line-range]- [What we're working on] - Pattern Reference:
[example-file:line]- [Similar implementation to follow] - Utility Available:
[helper-file:line]- [Existing code that can help] - Integration Point:
[interface-file:line]- [Where this connects to other components]
Quality Assurance Checklist
Architecture Considerations
- Pattern Consistency: [Specific pattern alignment check]
- Separation of Concerns: [Component responsibility verification]
- Integration: [How this fits with existing system]
Implementation Quality
- Error Handling: [Specific error scenarios to address]
- Edge Cases: [Boundary conditions to consider]
- Performance: [Optimization opportunities or concerns]
- Security: [Security considerations for this implementation]
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.
- 4d ago First seen · 173 lines · 0 tokens per session scan A 3a73433861fa
codex-navigator.template is an agent published in the GitHub repository Fomo-Driven-Development/strategic-claude-base (2 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,299 tokens. 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.