Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add upex-galaxy/agentic-qa-boilerplate --skill agentic-qa-coregit clone --depth 1 https://github.com/upex-galaxy/agentic-qa-boilerplateWrote 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/agentic-qa-core)<a href="https://agentmods.dev/skills/upex-galaxy/agentic-qa-boilerplate/agentic-qa-core"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/agentic-qa-core/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/agentic-qa-core"><img src="https://agentmods.dev/badge/skills/upex-galaxy/agentic-qa-boilerplate/agentic-qa-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00115 | $0.02732 |
| Opus 5 | $0.00057 | $0.01366 |
| Sonnet 5 | $0.00023 | $0.00546 |
| Haiku 4.5 | $0.00012 | $0.00273 |
Grade A, and why
agentic-qa-core scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `references/api-testing-doctrine.md` | `sprint-testing`, `test-automation`, `test-documentation` | **Canonical API-testing maneuver** (agentic level, not KATA code): the three-tool split — OpenAPI MCP = schema READ-ONL How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic QA Core — Foundation reference host
agentic-qa-core is the shared reference library that every workflow skill in this repo cites. It exists so doctrine (briefing template, dispatch patterns, orchestration rules, skill composition tiers) lives in one place instead of being duplicated across every SKILL.md.
Loading a workflow skill (e.g. shift-left-testing, sprint-testing, test-automation) implies loading the relevant agentic-qa-core/references/*.md on demand — workflow skills declare a ## Dependencies block at the top so the AI knows what to pull in.
This skill does NOT orchestrate workflows, does NOT generate files, and does NOT bootstrap a target repo. The entire framework (skills, foundation files, scripts) ships together as one repo; à la carte adoption is not supported — see "Install model" below.
Compact Rules
- DO NOT create, modify, or delete ANY file while acting as
agentic-qa-core. It is a passive reference library with no write path of its own. - DO NOT write
.context/artifacts here (that is/project-discovery), scaffold tests / fixtures / KATA components (that is/adapt-frameworkand/test-automation), adapt the framework to a stack (/adapt-framework), sync AI-critical docs (/sync-ai-context), or sync OpenAPI schemas (bun run api:sync). - DO NOT orchestrate a workflow or bootstrap a target repo from this skill. It hosts doctrine; the workflow skills execute it.
- WHEN a workflow skill cites
agentic-qa-core/references/*.md: load ONLY the files that skill's## Dependenciesblock names. Never preload the whole reference set. - WHEN deriving test cases or coverage from acceptance criteria in ANY testing skill:
references/test-design-doctrine.mdis mandatory reading first. - WHEN filing any bug / defect / improvement:
references/defect-management-doctrine.mdis mandatory reading first. - WHEN dispatching a subagent: use the 7-component briefing in
references/briefing-template.mdand pick the pattern viareferences/dispatch-patterns.md. A subagent that must answer the user directly also loadsreferences/behavioral-layer.md— it inherits no register from the orchestrator. - WHEN closing a workflow stage: verify that stage's Definition of Done in
references/stage-gates.mdBEFORE advancing. - DO edit the owning skill's
references/*.mdwhen a rule changes, then runbun run skills:registry, then refresh the deck underpackages/decks/agentic-qa-core/. That order keeps prose, registry, and decks from drifting. - DO treat this boilerplate as clone-in-full. Copying a single skill directory in isolation leaves it without the foundation files it depends on, and it will not function.
What ships with it
18 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.
- references/acli-integration.md 13 KB
- references/adr-doctrine.md 7.7 KB
- references/api-testing-doctrine.md 7.5 KB
- references/behavioral-layer.md 2.0 KB
- references/briefing-template.md 11 KB
- references/defect-management-doctrine.md 22 KB
- references/dispatch-patterns.md 5.3 KB
- references/evidence-conventions.md 5.0 KB
- references/jira-publishing-gotchas.md 6.8 KB
- references/orchestration-doctrine.md 2.6 KB
- references/preflight-gate.md 13 KB
- references/session-footer-contract.md 6.1 KB
- references/session-management.md 26 KB
- references/skill-composition-strategy.md 31 KB
- references/skill-resolver.md 9.7 KB
- references/stage-gates.md 7.8 KB
- references/test-design-doctrine.md 14 KB
- references/traceability-linking.md 27 KB
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 · 115 lines · 115 tokens per session scan A 8fcc89349322
agentic-qa-core is a skill published in the GitHub repository upex-galaxy/agentic-qa-boilerplate (21 stars, last pushed 4d ago), licensed MIT. It adds 115 tokens to every session and 2,732 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.
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.
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.
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.
skill-testing
Test skills for correct activation, content quality, and regression — both automated checks (frontmatter validity, lint) and manual verification (query-suite activation testing). Covers CI integration and how to catch skill regressions before users do. Use this skill when adding skills to a repo, setting up CI for a…