Borrowing it
Nothing to install: this file belongs to CGSOG-JumpStarts/JumpStart-AutoNav. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CGSOG-JumpStarts/JumpStart-AutoNav/main/CLAUDE.mdgit 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/instructions/cgsog-jumpstarts/jumpstart-autonav/claude-md)<a href="https://agentmods.dev/instructions/cgsog-jumpstarts/jumpstart-autonav/claude-md"><img src="https://agentmods.dev/badge/instructions/cgsog-jumpstarts/jumpstart-autonav/claude-md/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/instructions/cgsog-jumpstarts/jumpstart-autonav/claude-md"><img src="https://agentmods.dev/badge/instructions/cgsog-jumpstarts/jumpstart-autonav/claude-md.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.01210 | $0.01210 |
| Opus 5 | $0.00605 | $0.00605 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
JumpStart-AutoNav CLAUDE.md 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 7d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jump Start Framework Instructions
This repository 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, method parameters, or return types
- Configuration flags, options, or environment variables
- Version compatibility, breaking changes, or migration guides
- Setup instructions, installation steps, or prerequisites
- Feature availability or deprecation status
How to use Context7:
- Resolve the library ID: Use
mcp_context7_resolve-library-idwithlibraryNameandqueryparameters - Fetch current docs: Use
mcp_context7_query-docswithlibraryId(e.g.,/vercel/next.js) andqueryparameters - Cite your source: Add
[Context7: library@version]marker in your output
Full documentation:
.jumpstart/guides/context7-usage.md
When is this required?
- Architect Phase 3: Documentation Freshness Audit before approval
- Developer Phase 4: Before writing any external API integration code
- Analyst Phase 1: When evaluating competitive technologies
- Any agent: When making claims about what a technology can or cannot do
Spec-First Power Inversion (Item 4)
Specs are the source of truth. Code is derived. If there is a mismatch between a spec artifact and the codebase, update the spec first or regenerate the code. Never silently alter code to diverge from specs.
Slash Command Routing
| Command | Action |
|---|---|
/jumpstart.scout |
Check project.type is brownfield. Load .jumpstart/agents/scout.md. Follow Reconnaissance Protocol. Output to specs/codebase-context.md. |
/jumpstart.challenge [idea] |
Load .jumpstart/agents/challenger.md. Follow the Elicitation Protocol. Output to specs/challenger-brief.md. |
/jumpstart.analyze |
Verify Phase 0 approved. Load .jumpstart/agents/analyst.md. Output to specs/product-brief.md. |
/jumpstart.plan |
Verify Phases 0-1 approved. Load .jumpstart/agents/pm.md. Output to specs/prd.md. |
/jumpstart.architect |
Verify Phases 0-2 approved. Load .jumpstart/agents/architect.md. Output to specs/architecture.md, specs/implementation-plan.md, specs/decisions/*.md. |
/jumpstart.build |
Verify Phases 0-3 approved. Load .jumpstart/agents/developer.md. Output code to src/, tests to tests/. |
/jumpstart.pitcrew |
Load .jumpstart/agents/facilitator.md. Launch multi-agent roundtable discussion. Advisory only — no artifact writes. |
/jumpstart.resume |
Read .jumpstart/state/state.json + insights. Present session resumption briefing (TLDR, where you left off, what's next, key insights, open questions). No artifact writes. |
/jumpstart.status |
Read config and all spec files. Report phase completion status. |
/jumpstart.review |
Validate current artifacts against templates. Report gaps. |
/jumpstart.install <id> |
Install a skill, agent, prompt, or bundle from the Skills marketplace registry. Supports skill ignition or skill.ignition syntax. Auto-resolves dependencies. |
/jumpstart.install --search <q> |
Search the marketplace for items matching a keyword, tag, or category. |
/jumpstart.status (marketplace) |
List all installed marketplace items with versions and locations. |
/jumpstart.uninstall <id> |
Uninstall a marketplace item and its remapped agent/prompt files. |
/jumpstart.update [<id>] |
Update installed items to the latest registry version. |
/jumpstart.timeline |
View, query, export, or clear the interaction timeline. Supports summary, report (markdown/json/html), query (filter by phase/agent/type), and clear. |
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.
- 7d ago First seen · 63 lines · 1,210 tokens per session scan A 7a7843f09f40
JumpStart-AutoNav CLAUDE.md is an instructions file published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 4mo ago), licensed MIT. It adds 1,210 tokens to every session, about $0.0060 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-09-03.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).