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.
git clone --depth 1 https://github.com/benallfree/vibescaleWrote 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/rules/benallfree/vibescale/navigo)<a href="https://agentmods.dev/rules/benallfree/vibescale/navigo"><img src="https://agentmods.dev/badge/rules/benallfree/vibescale/navigo/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/rules/benallfree/vibescale/navigo"><img src="https://agentmods.dev/badge/rules/benallfree/vibescale/navigo.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.00008 | $0.01129 |
| Opus 5.5 | $0.00003 | $0.00452 |
| Sonnet 5.5 | $0.00002 | $0.00226 |
| Haiku 4.5 | $0.00001 | $0.00113 |
Grade A, and why
navigo 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 2mo 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Navigo Router Documentation
Quick Reference
Installation and Initialization
const router = new Navigo('/root/path', {
strategy: 'ONE' | 'ALL', // Default: 'ONE'
noMatchWarning: boolean, // Default: false
})
Core Methods
| Method | Description | Example |
|---|---|---|
on() |
Register routes | router.on('/path', handler) |
navigate() |
Navigate with URL change | router.navigate('/path') |
resolve() |
Navigate without URL change | router.resolve() |
notFound() |
Handle 404 routes | router.notFound(handler) |
destroy() |
Remove all routes | router.destroy() |
Detailed Guide
Route Registration Methods
- Single Route
router.on('/foo/bar', () => {
// Handler for '/foo/bar'
})
- Root Route
router.on(() => {
// Handler for root path
})
- Multiple Routes Map
router.on({
'/foo/bar': () => {
/* handler */
},
'/foo/baz': () => {
/* handler */
},
})
- Named Routes
router.on({
'/foo/bar': {
as: 'routeName',
uses: () => {
/* handler */
},
},
})
Route Hooks
Hook Types
type RouteHooks = {
before?: (done: Function, match: Match) => void
after?: (match: Match) => void
leave?: (done: Function, match: Match) => void
already?: (match: Match) => void
}
Adding Hooks
- Route-Specific Hooks
router.on('/path', handler, {
before: (done, match) => {
// Pre-route logic
done() // Continue
// done(false); // Cancel navigation
},
after: (match) => {
// Post-route logic
},
})
- Global Hooks
router.hooks({
before: (done, match) => {
// Global pre-route logic
done()
},
})
Navigation Options
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.
- 2mo ago First seen · 257 lines · 8 tokens per session scan A 5c17d8d89f96
navigo is a cursor rule published in the GitHub repository benallfree/vibescale (4 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 1,129 once invoked, about $0.0000 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-08-31.
Other cursor rules, from other repositories
writing-tests
How to write tests in the monorepo.
browser-extension
Browser extension patterns and development practices.
coverage-thresholds
Coverage threshold configuration patterns.
process-management
Process management and zombie process prevention patterns.
server-security
Browser input is untrusted. All project filesystem access goes through ProjectService.resolveProjectPath → ProjectRootGuard.resolveSafe. Do not call path.resolve/readFile/writeFile on user-influenced paths without that guard.
typescript
TypeScript conventions for this monorepo (strict mode, Zod boundaries, package imports, naming). Apply when editing .ts/.tsx files.