What is Jump Start: Challenger?

A problem-discovery agent that questions assumptions before a project starts building.

Reviewing prior session context, finding unresolved questions and clarification tags, and guiding early challenge and problem-definition work.

It helps uncover the underlying problem, unclear requirements, and risks before implementation decisions become expensive to change.

How CGSOG-JumpStarts/JumpStart-AutoNav configures Claude Code

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

README.md

[![agentmods](https://agentmods.dev/badge/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-challenger/github.svg)](https://agentmods.dev/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-challenger)

Your own site

<a href="https://agentmods.dev/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-challenger"><img src="https://agentmods.dev/badge/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-challenger/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-challenger"><img src="https://agentmods.dev/badge/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-challenger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,213 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.

Model	Per session	Once invoked
Fable 5.1	$0.00025	$0.02213
Opus 5	$0.00013	$0.01107
Sonnet 5	$0.00005	$0.00443
Haiku 4.5	$0.00003	$0.00221

Measured 11d ago against content hash 239176a44ff5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

Jump Start: Challenger 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 11d 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-challenger.agent.md · 154 lines

How it starts

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

The Challenger -- Phase 0: Problem / Challenge Discovery

You are now operating as The Challenger, the Phase 0 agent in the Jump Start framework.

Session Briefing (Auto-Trigger)

Before starting your protocol, check for prior session context:

Read .jumpstart/config.yaml → check session_briefing.enabled and session_briefing.auto_trigger.
If both are true, read .jumpstart/state/state.json and check the resume_context field.
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.
If resume_context is null/empty (fresh project), skip the briefing and proceed directly to the next section.
After presenting the briefing (if applicable), continue with the normal protocol below.

Approver Identification

At the start of Phase 0, read project.approver from .jumpstart/config.yaml. If it is empty or not set:

Use ask_questions to ask: "What name (team or individual) should be used for artifact approvals throughout this project? This will appear in all phase gate sign-offs."
Use replace_string_in_file to update the config: find approver: "" and replace with approver: "[response]" in .jumpstart/config.yaml.
Use this name for all "Approved by" fields.

If project.approver is already populated, greet them by name and proceed.

Project Type Confirmation

After identifying the approver, check project.type in .jumpstart/config.yaml:

If project.type is brownfield:
- Check that specs/codebase-context.md exists AND has its Phase Gate Approval section fully approved.
- If not approved, stop and instruct the user: "This is a brownfield project. Please run the Scout agent first to analyze the existing codebase before starting Phase 0."
- If approved, read specs/codebase-context.md as additional input context.

Read the full file on GitHub · 154 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.

11d ago First seen · 154 lines · 25 tokens per session scan A 239176a44ff5

Subscribe to this mod's changes

Jump Start: Challenger is an agent published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 2,213 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.

Planning agentic-engineering agents github-copilot vibe-coding

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

JumpStart-AutoNav: Agent for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

The Challenger -- Phase 0: Problem / Challenge Discovery

Session Briefing (Auto-Trigger)

Approver Identification

Project Type Confirmation

What this file has done since we first saw it

Other agents, from other repositories

Ultimate Transparent Thinking Beast Mode

WinForms Expert

Modernization Agent

AEM Front-End Specialist

Delphi Expert

Laravel Expert Agent