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.
git clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplatenpx agentmods add skills/upex-galaxy/agentic-qa-boilerplate/shift-left-testingWrote 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/skills/upex-galaxy/agentic-qa-boilerplate/shift-left-testing)<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.
<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>- NVIDIA SkillSpector warn
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.
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.00303 | $0.13327 |
| Opus 5.5 | $0.00121 | $0.05331 |
| Sonnet 5.5 | $0.00061 | $0.02665 |
| Haiku 4.5 | $0.00030 | $0.01333 |
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.
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.
- The business context skills
business-e2e-context+business-data-context+business-api-context, read throughbun 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.) .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.- The Story's Acceptance Criteria +
**Source spec:**reference on Jira. Detailed read viabun run jira:sync-issues get <STORY_KEY> --include-comments, then read the syncedacceptance-criteria.md(+ description). NEVERacli viewfor custom fields. Canonical input — every refined AC must trace back here. .context/PBI/epics/EPIC-<KEY>-<slug>/stories/STORY-<KEY>-<slug>/if a PBI folder already exists for this Story (created by a prior/sprint-testingcycle). Carries earlier session notes worth honoring..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 Reviewtracking 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..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.
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.
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 Changed 2a630a95eb61
- 17d ago Changed 7a66fffa9fb0
- 18d ago Changed 2b46c3c71b58
- 20d ago Changed · +1 lines 4e6ee4347674
- 22d ago Changed 58b6dc5e62ca
- 27d ago Changed · +2 lines 813fc2c3172a
- 28d ago Changed · -2 lines 433c543185df
- 29d ago Changed · +2 lines c5b7917a5143
- 1mo ago Changed 1be8b09d4a4e
- 1mo ago First seen · 530 lines · 303 tokens per session scan A 2f179f588b5f
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.
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.
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.
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.
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.
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.
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…