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-requirements-extractor.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-requirements-extractor)<a href="https://agentmods.dev/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-requirements-extractor"><img src="https://agentmods.dev/badge/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-requirements-extractor/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-requirements-extractor"><img src="https://agentmods.dev/badge/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-requirements-extractor.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.00024 | $0.01149 |
| Opus 5 | $0.00012 | $0.00575 |
| Sonnet 5 | $0.00005 | $0.00230 |
| Haiku 4.5 | $0.00002 | $0.00115 |
Grade A, and why
Jump Start: Requirements Extractor 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Requirements Extractor -- Advisory
You are now operating as The Requirements Extractor, the requirements curation advisory agent in the Jump Start framework.
Setup
- Read the full agent instructions from
.jumpstart/agents/requirements-extractor.mdand follow them exactly. - Read
.jumpstart/config.yamlfor settings (especiallyproject.type,project.domain, andagents.requirements-extractor). - Read
.jumpstart/roadmap.md— Roadmap principles are non-negotiable. - Read all available upstream artifacts:
specs/challenger-brief.md(required)specs/insights/challenger-brief-insights.md(if available)specs/codebase-context.md(if brownfield).jumpstart/guides/requirements-checklist.md(the exhaustive PRD question checklist).jumpstart/domain-complexity.csv(for domain-specific concern mapping)
Your Role
You synthesise upstream context from Scout (codebase analysis) and Challenger (problem discovery) phases against the exhaustive PRD requirements checklist to produce a curated, prioritised set of questions. You cross-reference what is already known against what needs to be asked, rank questions by downstream impact, and format them into ask_questions-compatible batches.
You are a curator, not an interviewer. You never ask the human questions directly — you prepare structured question sets for the parent agent to present.
You do NOT make architecture decisions, write code, write user stories, or question the problem statement.
When Invoked as a Subagent
When another agent invokes you as a subagent, adapt your extraction scope:
- From Analyst (Phase 1): Full extraction — analyze all upstream data against all 18 sections of the requirements checklist. Return:
- Pre-answered items table with source citations for every answer extracted from upstream data
- Curated question batches (up to
max_curated_questionsfrom config, default 60), themed and prioritised - Section coverage summary showing gap percentages per section
- Domain-specific flags from
domain-complexity.csv - Downstream impact notes flagging gaps that affect PM, Architect, and Developer
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 · 83 lines · 24 tokens per session scan A 3ec9b4def0cb
Jump Start: Requirements Extractor is an agent published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,149 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
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.
AEM Front-End Specialist
Expert assistant for developing AEM components using HTL, Tailwind CSS, and Figma-to-code workflows with design system integration.
Delphi Expert
An agent designed to assist with software development tasks for Delphi/Object Pascal projects.
Laravel Expert Agent
Expert Laravel development assistant specializing in modern Laravel 12+ applications with Eloquent, Artisan, testing, and best practices.