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/.github/copilot-instructions.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/copilot-instructions)<a href="https://agentmods.dev/instructions/cgsog-jumpstarts/jumpstart-autonav/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/cgsog-jumpstarts/jumpstart-autonav/copilot-instructions/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/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/cgsog-jumpstarts/jumpstart-autonav/copilot-instructions.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.01357 | $0.01357 |
| Opus 5 | $0.00678 | $0.00678 |
| Sonnet 5 | $0.00271 | $0.00271 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade A, and why
JumpStart-AutoNav copilot-instructions.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 10d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Jump Start Framework
This project uses the Jump Start spec-driven agentic coding framework. Development follows five sequential phases, each owned by a specialized AI agent.
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: Use
mcp_context7_resolve-library-idwithlibraryNameandqueryparameters - Fetch current docs: Use
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 (Documentation Freshness Audit — hard gate, ≥80% score), Developer Phase 4 (before writing external API integration code), Analyst Phase 1 (technology evaluation), any agent making technology claims.
Spec-First Power Inversion
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.
Workflow
[Brownfield only] Pre-Phase (Scout) -> Phase 0 (Challenger) -> Phase 1 (Analyst) -> Phase 2 (PM) -> Phase 3 (Architect) -> Phase 4 (Developer)
Pit Crew (/jumpstart.pitcrew) can be invoked at any phase for multi-agent advisory discussions via the Facilitator agent.
Phases are strictly sequential. Each must be completed and approved by the human before the next begins. For brownfield projects (project.type: brownfield in config), the Scout agent runs before Phase 0 to analyze the existing codebase.
Key Directories
.jumpstart/agents/-- Detailed agent personas with step-by-step protocols (includes scout.md for brownfield).jumpstart/templates/-- Artifact templates that structure each phase's output (includes codebase-context.md, agents-md.md).jumpstart/schemas/-- JSON Schema (draft-07) definitions for artifact validation.jumpstart/config.yaml-- Framework settings (agent parameters, workflow rules, project type).jumpstart/roadmap.md-- Project Roadmap: non-negotiable principles that govern all agents.jumpstart/roadmap.md-- Engineering articles governing code quality and architecture decisions.jumpstart/invariants.md-- Environment invariants that must hold true in every deployment.jumpstart/domain-complexity.csv-- Domain complexity data for adaptive planning rigor.jumpstart/glossary.md-- Terminology dictionary: canonical term definitions for consistent naming.jumpstart/correction-log.md-- Self-correction log: rejected proposals and lessons learned.jumpstart/state/-- Workflow state persistence (state.json, todos.json, adr-index.json, locks/).jumpstart/archive/-- Timestamped archives of overwritten artifactsspecs/-- Generated specification artifacts (the source of truth for this project)specs/codebase-context.md-- Scout output for brownfield projects (existing codebase analysis with C4 diagrams)specs/decisions/-- Architecture Decision Recordsspecs/insights/-- Living insight logs (1:1 with each artifact)specs/qa-log.md-- Q&A decision log: audit trail of every agent question and human responsespecs/research/-- Optional research artifacts (competitive analysis, technical spikes)
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.
- 10d ago First seen · 73 lines · 1,357 tokens per session scan A 2f405d8eb2d0
JumpStart-AutoNav copilot-instructions.md is an instructions file published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 3mo ago), licensed MIT. It adds 1,357 tokens to every session, about $0.0068 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 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.
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).
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.