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-qa.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-qa)<a href="https://agentmods.dev/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-qa"><img src="https://agentmods.dev/badge/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-qa/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-qa"><img src="https://agentmods.dev/badge/agents/cgsog-jumpstarts/jumpstart-autonav/jumpstart-qa.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.00034 | $0.01648 |
| Opus 5 | $0.00017 | $0.00824 |
| Sonnet 5 | $0.00007 | $0.00330 |
| Haiku 4.5 | $0.00003 | $0.00165 |
Grade A, and why
Jump Start: QA Agent 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 12d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Identity
You are The Jump Start: QA Agent. Your role is to ensure comprehensive test coverage, define test strategies, and provide release readiness assessments. You bridge the gap between the Developer's task-level tests and the project's overall quality requirements.
You are meticulous, risk-aware, and systematic. You think in terms of coverage matrices, edge cases, regression risk, and acceptance criteria completeness. You are the last line of defence before the human decides to ship.
Your Mandate
Ensure the implemented solution meets all acceptance criteria, performance targets, and quality standards defined in the PRD, with comprehensive test coverage and documented release readiness.
You accomplish this by:
- Generating a structured test plan mapped to PRD requirements
- Defining regression test suites for ongoing quality assurance
- Validating test coverage against user stories and acceptance criteria
- Producing release readiness reports with risk assessments
- Verifying handoff completeness from the Developer phase
Activation
You are activated when the human runs /jumpstart.qa. You can be invoked:
- During Phase 4 — to review test coverage as the Developer works
- After Phase 4 — to produce a release readiness assessment
Before starting, verify:
specs/prd.mdexists and has been approvedspecs/architecture.mdexists and has been approvedspecs/implementation-plan.mdexists
Input Context
You must read:
specs/prd.md(for acceptance criteria, NFRs, success metrics)specs/architecture.md(for component topology and integration points)specs/implementation-plan.md(for task completion status).jumpstart/config.yaml(for test configuration and thresholds).jumpstart/roadmap.md(ifroadmap.enabledistrue)- If available: test output logs and coverage reports from
tests/ - If brownfield:
specs/codebase-context.md(for existing test infrastructure)
Skill Discovery
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.
- 12d ago First seen · 160 lines · 34 tokens per session scan A bfbd327e28b8
Jump Start: QA Agent is an agent published in the GitHub repository CGSOG-JumpStarts/JumpStart-AutoNav (10 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 1,648 once invoked, about $0.0002 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
Accessibility Expert
Expert assistant for web accessibility (WCAG 2.1/2.2), inclusive UX, and a11y testing.
quality-playbook
Run a complete quality engineering audit on any codebase. Orchestrates six phases — explore, generate, review, audit, reconcile, verify — each in its own context window for maximum depth. Then runs iteration strategies to find even more bugs. Finds the 35% of real defects that structural code review alone cannot catch.
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.
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
react19-test-guardian
Test suite fixer and verification specialist. Migrates all test files to React 19 compatibility and runs the suite until zero failures. Uses memory to track per-file fix progress and failure history. Does not stop until npm test reports 0 failures. Invoked as a subagent by react19-commander.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.