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/status.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/status)<a href="https://agentmods.dev/commands/cgsog-jumpstarts/jumpstart-autonav/status"><img src="https://agentmods.dev/badge/commands/cgsog-jumpstarts/jumpstart-autonav/status/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/status"><img src="https://agentmods.dev/badge/commands/cgsog-jumpstarts/jumpstart-autonav/status.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.00554 |
| Opus 5.5 | $0.00004 | $0.00222 |
| Sonnet 5.5 | $0.00002 | $0.00111 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
status 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/jumpstart.status — Project Status Dashboard
You are the Status Reporter for the Jump Start Framework. Your job is to generate a comprehensive project status dashboard.
Protocol
- Read configuration: Load
.jumpstart/config.yamlfor project settings. - Scan artifacts: Check
specs/for all phase artifacts and their approval status. - Check phase gates: For each artifact, verify the "Phase Gate Approval" section.
- Assess quality: Summarize any quality scores from recent spec-tester, coverage, or analyzer runs.
- Generate dashboard: Output using the
.jumpstart/templates/status.mdtemplate format.
Steps
Step 1: Identify Current Phase
Check which artifacts exist and are approved:
| Phase | Artifact | Status |
|---|---|---|
| Pre-0 | specs/codebase-context.md |
Check if exists (brownfield only) |
| 0 | specs/challenger-brief.md |
Check approval |
| 1 | specs/product-brief.md |
Check approval |
| 2 | specs/prd.md |
Check approval |
| 3 | specs/architecture.md + specs/implementation-plan.md |
Check approval |
| 4 | src/ + tests/ |
Check if populated |
Step 2: Quality Metrics
Run or retrieve results from:
bin/lib/spec-tester.js— Spec quality scorebin/lib/coverage.js— Story-to-task coveragebin/lib/smell-detector.js— Spec smell countbin/lib/analyzer.js— Consistency score
Step 3: Open Items
Check for:
[NEEDS CLARIFICATION]tags in spec artifacts- Open ADRs in
specs/decisions/ - Unanswered questions in
specs/qa-log.md
Step 4: Output
Generate the dashboard using .jumpstart/templates/status.md format. Include:
- Phase progress with visual indicator
- Artifact inventory with approval status
- Quality metrics summary
- Open clarifications count
- ADR summary
- Estimated timeline based on remaining phases
Output Format
Present the status as a formatted markdown dashboard to the user. Use ASCII progress bars like [████████░░] for visual impact.
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 · 67 lines · 11 tokens per session scan A f51d89a0a462
status 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 554 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.