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 rules/cgsog-jumpstarts/jumpstart-autonav/cursorrulesgit clone --depth 1 https://github.com/CGSOG-JumpStarts/JumpStart-AutoNavWrote 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/cgsog-jumpstarts/jumpstart-autonav/cursorrules)<a href="https://agentmods.dev/rules/cgsog-jumpstarts/jumpstart-autonav/cursorrules"><img src="https://agentmods.dev/badge/rules/cgsog-jumpstarts/jumpstart-autonav/cursorrules.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.1 | $0.00627 | $0.00627 |
| Opus 5 | $0.00313 | $0.00313 |
| Sonnet 5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
cursorrules 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 6d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jump Start Framework Rules
This project uses the Jump Start spec-driven agentic coding framework.
Context7 MCP Mandate (HIGH PRIORITY)
CRITICAL RULE: When referencing any external library, framework, CLI tool, or service — you MUST use Context7 MCP to fetch live, verified documentation. Never rely on training data for API signatures, configuration flags, version compatibility, or setup instructions.
How to use Context7:
- Resolve the library ID:
mcp_context7_resolve-library-idwithlibraryNameandqueryparameters - Fetch current docs:
mcp_context7_query-docswithlibraryId(e.g.,/vercel/next.js) andqueryparameters - Add
[Context7: library@version]citation marker in output
Full documentation:
.jumpstart/guides/context7-usage.md
When required: Architect Phase 3 (freshness audit), Developer Phase 4 (external API code), Analyst Phase 1 (tech evaluation), any agent making technology claims.
Spec-First Power Inversion
Specs are the source of truth. Code is derived. If mismatch exists between spec and code, update the spec first or regenerate the code. Never silently diverge.
Command Routing
/jumpstart.scout-> Checkproject.typeisbrownfield. Read and follow.jumpstart/agents/scout.md/jumpstart.challenge-> Read and follow.jumpstart/agents/challenger.md/jumpstart.analyze-> Read and follow.jumpstart/agents/analyst.md/jumpstart.plan-> Read and follow.jumpstart/agents/pm.md/jumpstart.architect-> Read and follow.jumpstart/agents/architect.md/jumpstart.build-> Read and follow.jumpstart/agents/developer.md/jumpstart.pitcrew-> Read and follow.jumpstart/agents/facilitator.md(Pit Crew: multi-agent collaboration)/jumpstart.status-> Check all spec files and report workflow state/jumpstart.review-> Validate artifacts against templates
Rules
- Phases are sequential. Do not start a phase unless all preceding phases are approved.
- Follow agent personas exactly. Read the agent file before starting.
- Always ask for explicit human approval between phases.
- Use templates from
.jumpstart/templates/. - Read
.jumpstart/config.yamlfor settings. - Specs go in
specs/. Code insrc/. Tests intests/. - Read
.jumpstart/roadmap.mdat activation. Roadmap principles are non-negotiable and supersede agent-specific instructions. - Read
.jumpstart/roadmap.mdfor engineering articles governing code quality and architecture decisions. - Use Context7 MCP for ALL external documentation lookups. Never guess API details from training data.
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.
- 6d ago First seen · 45 lines · 627 tokens per session scan A da8ffbcb33f8
cursorrules is a cursor rule published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 3mo ago), licensed MIT. It adds 627 tokens to every session, about $0.0031 per session on Opus 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.