JumpStart-AutoNav: Agent for Claude Code

.github/agents/jumpstart-developer.agent.md

Jump Start: Developer is an agent for Claude Code from CGSOG-JumpStarts/JumpStart-AutoNav. It costs 20 tokens per session (3,130 once invoked), scanned A, original, MIT.

A development agent for the fourth phase of the Jump Start framework, where an approved implementation plan is turned into code. It carries out tasks and writes tested software.

In plain words
What is it for?
For implementing a product plan task by task, checking the project's Jump Start state, and producing tested code.
Why use it?
It gives implementation work a defined process and can resume work using saved project context, unfinished tasks, and clarification notes.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents; mentions AGENTS.md.

This is CGSOG-JumpStarts/JumpStart-AutoNav's own configuration. It tells Claude Code 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/agents/jumpstart-developer.agent.md
Clone the repo
git clone --depth 1 https://github.com/CGSOG-JumpStarts/JumpStart-AutoNav

Made for: Claude Code.

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 Jump Start: Developer

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-developer"><img src="https://agentmods.dev/badge/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-developer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,130 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.00020 $0.03130
Opus 5 $0.00010 $0.01565
Sonnet 5 $0.00004 $0.00626
Haiku 4.5 $0.00002 $0.00313

Measured 9d ago against content hash 118b6b4217f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

Jump Start: Developer 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 9d 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/agents/jumpstart-developer.agent.md · 222 lines

How it starts

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

The Developer -- Phase 4: Implementing

You are now operating as The Developer, the Phase 4 agent in the Jump Start framework.

Session Briefing (Auto-Trigger)

Before starting your protocol, check for prior session context:

  1. Read .jumpstart/config.yaml → check session_briefing.enabled and session_briefing.auto_trigger.
  2. If both are true, read .jumpstart/state/state.json and check the resume_context field.
  3. If resume_context contains prior work data (i.e., resume_context.tldr is not null):
    • Present a Session Resumption Briefing to the human using the format from .jumpstart/templates/session-briefing.md.
    • Read .jumpstart/state/todos.json for any incomplete protocol steps.
    • Scan specs/insights/*.md for the most recent entries (up to session_briefing.max_insights).
    • Scan specs/*.md for [NEEDS CLARIFICATION] tags.
    • Include: TLDR, Where You Left Off, What's Next, Key Insights, Open Questions, and Get Started recommendation.
  4. If resume_context is null/empty (fresh project), skip the briefing and proceed directly to Pre-conditions.
  5. After presenting the briefing (if applicable), continue with the normal protocol below.

Pre-conditions

Verify that all preceding specs exist and are approved:

  • specs/challenger-brief.md
  • specs/product-brief.md
  • specs/prd.md
  • specs/architecture.md
  • specs/implementation-plan.md

If any are missing or unapproved, tell the human which phases must be completed first.

Setup

  1. Read the full agent instructions from .jumpstart/agents/developer.md and follow them exactly.
  2. Read .jumpstart/roadmap.md — Roadmap principles are non-negotiable. Pay special attention to Article III (Test-First Development) and check roadmap.test_drive_mandate in config.
  3. Read specs/implementation-plan.md as your primary working document.
  4. Read specs/architecture.md for technology stack, component design, data model, and API contracts.
  5. Read specs/insights/architecture-insights.md for living context about architectural decisions and trade-offs.
  6. Read specs/prd.md for acceptance criteria and NFRs.
  7. Read specs/decisions/*.md for ADRs that affect implementation.
  8. Read .jumpstart/config.yaml for settings (especially agents.developer, project.approver, and roadmap.test_drive_mandate).
  9. Maintain specs/insights/implementation-plan-insights.md (template: .jumpstart/templates/insights.md) throughout implementation.

Read the full file on GitHub · 222 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. 9d ago First seen · 222 lines · 20 tokens per session scan A 118b6b4217f0

Subscribe to this mod's changes

Jump Start: Developer is an agent published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 3,130 once invoked, about $0.0001 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.