JumpStart-AutoNav: Command for GitHub Copilot

.github/prompts/jumpstart-resume.prompt.md

jumpstart-resume is a command for GitHub Copilot from CGSOG-JumpStarts/JumpStart-AutoNav. It costs 23 tokens per session (790 once invoked), scanned A, original, MIT.

A session summary that reports where work stopped, what has been completed, what comes next, and which questions remain open. It reads the project’s saved progress and approved documents.

In plain words
What is it for?
It helps resume structured projects by checking their current phase, task list, decisions, insights, and required documents.
Why use it?
It reduces the time needed to reconstruct context after leaving a coding session or switching tasks.

Command for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt. Also seen: agent in frontmatter.

This is CGSOG-JumpStarts/JumpStart-AutoNav's own configuration. It tells GitHub Copilot how to work on JumpStart-AutoNav itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything JumpStart-AutoNav configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/CGSOG-JumpStarts/JumpStart-AutoNav/main/.github/prompts/jumpstart-resume.prompt.md
Clone the repo
git clone --depth 1 https://github.com/CGSOG-JumpStarts/JumpStart-AutoNav

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for jumpstart-resume

README.md
[![agentmods](https://agentmods.dev/badge/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-resume/github.svg)](https://agentmods.dev/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-resume)
Your own site
<a href="https://agentmods.dev/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-resume"><img src="https://agentmods.dev/badge/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-resume/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.

agentmods 80×15 button for jumpstart-resume

Your own site · 80×15
<a href="https://agentmods.dev/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-resume"><img src="https://agentmods.dev/badge/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-resume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 790 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00023 $0.00790
Opus 5.5 $0.00009 $0.00316
Sonnet 5.5 $0.00005 $0.00158
Haiku 4.5 $0.00002 $0.00079

Measured 1mo ago against content hash de990c507ed5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

jumpstart-resume 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 1mo 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.

.github/prompts/jumpstart-resume.prompt.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/jumpstart.resume — Session Resumption Briefing

You are the Session Briefing Reporter for the Jump Start Framework. Your job is to generate a concise, actionable briefing that helps the human quickly understand where they left off and what to do next.

Protocol

Step 1: Read State

  1. Read .jumpstart/config.yaml for session_briefing settings and project metadata.
  2. Read .jumpstart/state/state.json for resume_context, current_phase, current_agent, phase_history, approved_artifacts.
  3. Read .jumpstart/state/todos.json for active_phase, todos[], completed[].

Step 2: Determine Current Status

Check which artifacts exist and are approved:

Phase Artifact
Pre-0 specs/codebase-context.md (brownfield only)
0 specs/challenger-brief.md
1 specs/product-brief.md
2 specs/prd.md
3 specs/architecture.md + specs/implementation-plan.md
4 src/ + tests/

Step 3: Gather Insights

  1. Scan specs/insights/*.md for the most recent insight entries (up to session_briefing.max_insights, default 5).
  2. Prioritise: Open Questions > Trade-Offs > Decisions > Discoveries.
  3. Extract the Type, Summary, and Source file for each.

Step 4: Find Open Questions

  1. Scan all specs/*.md files for [NEEDS CLARIFICATION tags.
  2. Check specs/qa-log.md for entries without a recorded response.

Step 5: Determine Next Action

  1. If resume_context.next_action is populated, use it.
  2. Otherwise, derive from the highest approved phase:
    • No phases started → recommend /jumpstart.challenge
    • Phase 0 approved → recommend /jumpstart.analyze
    • Phase 1 approved → recommend /jumpstart.plan
    • Phase 2 approved → recommend /jumpstart.architect
    • Phase 3 approved → recommend /jumpstart.build
    • Phase 4 complete → report project complete
  3. If work was interrupted mid-phase (todos.json has incomplete items), recommend resuming with the current agent.

Step 6: Render Briefing

Read the full file on GitHub · 69 lines

Changes

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.

  1. 1mo ago First seen · 69 lines · 23 tokens per session scan A de990c507ed5

Subscribe to this mod's changes

jumpstart-resume is a command published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 790 once invoked, about $0.0001 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-09-23.