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/agents/jumpstart-developer.agent.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/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-developer)<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.
<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>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.00020 | $0.03130 |
| Opus 5 | $0.00010 | $0.01565 |
| Sonnet 5 | $0.00004 | $0.00626 |
| Haiku 4.5 | $0.00002 | $0.00313 |
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.
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:
- Read
.jumpstart/config.yaml→ checksession_briefing.enabledandsession_briefing.auto_trigger. - If both are
true, read.jumpstart/state/state.jsonand check theresume_contextfield. - If
resume_contextcontains prior work data (i.e.,resume_context.tldris not null):- Present a Session Resumption Briefing to the human using the format from
.jumpstart/templates/session-briefing.md. - Read
.jumpstart/state/todos.jsonfor any incomplete protocol steps. - Scan
specs/insights/*.mdfor the most recent entries (up tosession_briefing.max_insights). - Scan
specs/*.mdfor[NEEDS CLARIFICATION]tags. - Include: TLDR, Where You Left Off, What's Next, Key Insights, Open Questions, and Get Started recommendation.
- Present a Session Resumption Briefing to the human using the format from
- If
resume_contextis null/empty (fresh project), skip the briefing and proceed directly to Pre-conditions. - 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.mdspecs/product-brief.mdspecs/prd.mdspecs/architecture.mdspecs/implementation-plan.md
If any are missing or unapproved, tell the human which phases must be completed first.
Setup
- Read the full agent instructions from
.jumpstart/agents/developer.mdand follow them exactly. - Read
.jumpstart/roadmap.md— Roadmap principles are non-negotiable. Pay special attention to Article III (Test-First Development) and checkroadmap.test_drive_mandatein config. - Read
specs/implementation-plan.mdas your primary working document. - Read
specs/architecture.mdfor technology stack, component design, data model, and API contracts. - Read
specs/insights/architecture-insights.mdfor living context about architectural decisions and trade-offs. - Read
specs/prd.mdfor acceptance criteria and NFRs. - Read
specs/decisions/*.mdfor ADRs that affect implementation. - Read
.jumpstart/config.yamlfor settings (especiallyagents.developer,project.approver, androadmap.test_drive_mandate). - Maintain
specs/insights/implementation-plan-insights.md(template:.jumpstart/templates/insights.md) throughout implementation.
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.
- 9d ago First seen · 222 lines · 20 tokens per session scan A 118b6b4217f0
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.
Other agents, from other repositories
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
DiffblueCover
Expert agent for creating unit tests for java applications using Diffblue Cover.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
tests
Test strategy, generation, authoring, and repair across all layers.
Accessibility Expert
Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing.
react18-test-guardian
Test suite fixer and verifier for React 16/17 → 18.3.1 migration. Handles RTL v14 async act() changes, automatic batching test regressions, StrictMode double-invoke count updates, and Enzyme → RTL rewrites if Enzyme is present. Loops until zero test failures. Invoked as subagent by react18-commander.