shift-left-testing

shift-left-testing is a skill for Claude Code, Codex from upex-galaxy/agentic-qa-boilerplate. It costs 303 tokens per session (13,327 once invoked), scanned A, original, MIT.

A pre-sprint QA workflow for reviewing a group of backlog stories before development starts. It refines acceptance criteria, which are the conditions a story must meet, and identifies unclear or missing requirements.

In plain words
What is it for?
Use it to clarify stories, expose ambiguities, draft a test-plan outline, and give product and development teams actionable requirements before sprint work begins.
Why use it?
Finding gaps before a story enters a sprint is cheaper than discovering them after implementation. The workflow connects the refined criteria to the project's business maps, API contracts, and existing test planning.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; names the AskUserQuestion tool; installed under .agents/ (shared by several agents).

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is **On any subagent failure**: STOP, report the partial state (which Stories refined, which Jira mutations landed), present retry / skip-story / abort options. Do.

Good fit Use it to clarify stories, expose ambiguities, draft a test-plan outline, and give product and development teams actionable requirements before sprint work begins.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplate
agentmods
npx agentmods add skills/upex-galaxy/agentic-qa-boilerplate/shift-left-testing

Made for: Claude Code, Codex.

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 shift-left-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/shift-left-testing/github.svg)](https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/shift-left-testing)
Your own site
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/shift-left-testing"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/shift-left-testing/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 shift-left-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/shift-left-testing"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/shift-left-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 303 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 13,327 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Rogue Agent · line 193
    Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.
    Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
How audits are shown
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.00303 $0.13327
Opus 5.5 $0.00121 $0.05331
Sonnet 5.5 $0.00061 $0.02665
Haiku 4.5 $0.00030 $0.01333

Measured 11d ago against content hash 2a630a95eb61, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

shift-left-testing 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.

.agents/skills/shift-left-testing/SKILL.md · 533 lines

How it starts

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

Inputs

Read in order; stop earlier when the batch is small enough that later inputs add no signal.

  1. The business context skills business-e2e-context + business-data-context + business-api-context, read through bun run context:map <slug> — journeys and feature catalog, entity model, CRUD matrix, auth model + endpoint groups. Anchors refined ACs in real entities, flows, and API behavior. (All three are hard-required by the Readiness Preflight Gate + Phase 0.3.)
  2. .context/PBI/qa-artifacts/master-test-plan.md — regression Epic + in-scope modules. Tells the refinement whether the Story falls inside an already-prioritized area.
  3. The Story's Acceptance Criteria + **Source spec:** reference on Jira. Detailed read via bun run jira:sync-issues get <STORY_KEY> --include-comments, then read the synced acceptance-criteria.md (+ description). NEVER acli view for custom fields. Canonical input — every refined AC must trace back here.
  4. .context/PBI/epics/EPIC-<KEY>-<slug>/stories/STORY-<KEY>-<slug>/ if a PBI folder already exists for this Story (created by a prior /sprint-testing cycle). Carries earlier session notes worth honoring.
  5. .agents/jira-workflows.json — Story workflow + valid transitions (backlog -> shift_left_qa -> estimation). Source of {{jira.transition.story.*}} slugs used in Phase 3. ALSO the resolver for the [QA] Shift-Left Review tracking subtask: read it to confirm a subtask work type exists (+ its transitions) before Phase 1 creates any subtask; if the catalog has no subtask work type, the subtask steps are skipped with a warning — never blocked on.
  6. .agents/jira-required.yaml — canonical slug catalog. Source of {{jira.acceptance_test_plan}} and other Jira field slugs touched in handoff.

Forbidden invocations

NEVER invoke /sdd-* skills from this workflow. SDD is an optional user-installed ceremony; this skill ships self-contained and does not chain SDD under any condition. If you need to refactor KATA, fixtures, cli/, scripts/, or api/schemas/ pipeline, exit this skill first and invoke /framework-development.

Read the full file on GitHub · 533 lines

Files

What ships with it

5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago Changed 2a630a95eb61
  2. 17d ago Changed 7a66fffa9fb0
  3. 18d ago Changed 2b46c3c71b58
  4. 20d ago Changed · +1 lines 4e6ee4347674
  5. 22d ago Changed 58b6dc5e62ca
  6. 27d ago Changed · +2 lines 813fc2c3172a
  7. 28d ago Changed · -2 lines 433c543185df
  8. 29d ago Changed · +2 lines c5b7917a5143
  9. 1mo ago Changed 1be8b09d4a4e
  10. 1mo ago First seen · 530 lines · 303 tokens per session scan A 2f179f588b5f

Subscribe to this mod's changes

shift-left-testing is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (26 stars, last pushed 11d ago), licensed MIT. It adds 303 tokens to every session and 13,327 once invoked, about $0.0012 per session on Opus 5.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-30.

Related

Other skills, from other repositories

agent-testing-harness

Use this skill when testing AI agent systems. Activate when the user needs to test agent behavior, write tests for multi-agent systems, implement agent evaluation frameworks, create test harnesses for autonomous agents, or validate agent outputs systematically.

latestaiagents/agent-skills · 51 tokens

test-generation-patterns

Use this skill when generating tests with AI assistance. Activate when the user wants to create unit tests, integration tests, generate test cases, improve test coverage, write tests for existing code, or set up testing patterns for their project.

latestaiagents/agent-skills · 52 tokens

api-test-patterns

Write comprehensive API tests for REST and GraphQL endpoints. Use this skill when testing APIs, writing contract tests, or validating integrations. Activate when: api testing, REST test, GraphQL test, endpoint testing, integration test, postman, contract testing.

latestaiagents/agent-skills · 56 tokens

playwright-patterns

Write reliable, maintainable E2E tests with Playwright best practices. Use this skill when writing Playwright tests, debugging flaky tests, or setting up E2E automation. Activate when: playwright, e2e test, end-to-end, browser testing, UI automation, web testing.

latestaiagents/agent-skills · 64 tokens

test-case-design

Design comprehensive test cases with proper coverage and clear documentation. Use this skill when writing test cases, creating test suites, or improving test coverage. Activate when: test case, test scenario, test coverage, test design, write tests, BDD, gherkin.

latestaiagents/agent-skills · 57 tokens

regression-evals

Set up continuous regression evals so model/prompt/tool changes don't silently break existing behavior. Covers gating thresholds, CI integration, statistical significance, and response to regressions. Use this skill when deploying prompts to production, gating model upgrades, or noticing "it worked yesterday" in AI…

latestaiagents/agent-skills · 85 tokens