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/prompts/jumpstart-review.prompt.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/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-review)<a href="https://agentmods.dev/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-review"><img src="https://agentmods.dev/badge/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-review/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/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-review"><img src="https://agentmods.dev/badge/commands/cgsog-jumpstarts/jumpstart-autonav/jumpstart-review.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.00011 | $0.00294 |
| Opus 5.5 | $0.00004 | $0.00118 |
| Sonnet 5.5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
jumpstart-review 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.
What it actually says
Jump Start Artifact Review
Determine the current phase by reading .jumpstart/config.yaml and checking which spec files exist.
For the most recent phase's artifact(s):
- Read the artifact file from
specs/. - Read the corresponding template from
.jumpstart/templates/. - Compare them section by section. Identify:
- Missing sections that exist in the template but not the artifact
- Empty or placeholder fields (still containing
[bracket placeholders]) - Sections with insufficient content (e.g., a table with only the header row)
- Check the Phase Gate Approval section for unchecked items.
- For Phase 2 (PRD): verify every Must Have story has at least 2 acceptance criteria.
- For Phase 3 (Architecture): verify every tech choice has a justification and every PRD story maps to an implementation task.
- For brownfield projects: verify
specs/codebase-context.mdexists and is approved before any other artifact. Check that brownfield-specific sections (existing system constraints, migration considerations) are addressed in downstream artifacts. - For greenfield projects in Phase 3: verify the implementation plan includes
[D]documentation tasks for per-directoryAGENTS.mdfiles.
Report findings with specific guidance on what needs to be fixed before the artifact can be approved.
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.
- 1mo ago First seen · 25 lines · 11 tokens per session scan A 7acc3821887d
jumpstart-review is a command published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 294 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-09-23.
Other commands, from other repositories
feedback
File a structured feedback entry when a downstream stage discovers an upstream .forge/ artifact needs revision.
spec
Create a PRD via interview and codebase exploration, output as .forge/prd.md.
prime
Load AI-optimized workflow context for beads issue tracking.
ready
Find ready-to-work tasks with no blockers.
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
daily-standup
Génération Résumé Daily Stand-up.