AGENTS.quality-testing

AGENTS.quality-testing is an agent for coding agents from jeremylongworth-source/AgentSkills. It costs 0 tokens per session (295 once invoked), scanned A, original, MIT.

A routing guide for software quality and testing work that directs unit, integration, end-to-end, accessibility, performance, regression, and release-readiness tasks to local skills.

In plain words
What is it for?
Use it to create unit-test cases, plan service and API tests, test complete browser or CLI journeys, reproduce bugs, build QA matrices, and define accessibility or performance checks.
Why use it?
It helps match a testing question to the right level of coverage. It also brings together checks for user journeys, devices, permissions, accessibility, speed, and release risk.

Agent

Install

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.

agentmods
npx agentmods add agents/jeremylongworth-source/agentskills/agents.quality-testing
Clone the repo
git clone --depth 1 https://github.com/jeremylongworth-source/AgentSkills

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 AGENTS.quality-testing

README.md
[![agentmods](https://agentmods.dev/badge/agents/jeremylongworth-source/agentskills/agents.quality-testing.svg)](https://agentmods.dev/agents/jeremylongworth-source/agentskills/agents.quality-testing)
Your own site
<a href="https://agentmods.dev/agents/jeremylongworth-source/agentskills/agents.quality-testing"><img src="https://agentmods.dev/badge/agents/jeremylongworth-source/agentskills/agents.quality-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 295 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00295
Opus 5 $0.00000 $0.00148
Sonnet 5 $0.00000 $0.00059
Haiku 4.5 $0.00000 $0.00030

Measured 3d ago against content hash 4d0c6fe2f658, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

AGENTS.quality-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 3d 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/AGENTS.quality-testing.md · 32 lines

What it actually says

Use local skills as the primary routing layer for quality and testing work.

Use unit-test-generation for focused unit cases, fixtures, mocks, edge cases, and regression guards.

Use integration-test-plan for component, API, database, queue, auth, service, and dependency-boundary tests.

Use e2e-test-plan for release-critical user journeys, browser flows, CLI workflows, smoke tests, assertions, and flake risks.

Use bug-reproduction when turning bug reports into observed/expected behavior, minimal reproduction steps, diagnostic checks, and regression targets.

Use qa-matrix when organizing release coverage across roles, devices, platforms, scenarios, permissions, data states, and risk areas.

Use accessibility-test-plan for keyboard, focus, screen reader, contrast, ARIA, forms, motion, caption, and accessibility release gates.

Use performance-test-plan for latency, load, throughput, Core Web Vitals, database/query, job, resource, and regression performance checks.

Use qa-test-strategy, regression-check, backend-test-plan, accessibility-inclusive-design, release-launch-readiness, and concise-technical-writing for broader QA strategy, regression gates, backend coverage, accessibility expertise, launch readiness, and summaries.

Do not claim tests passed without evidence. Do not use production data, credentials, or live systems for tests without explicit approval.

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. 3d ago First seen · 32 lines · 0 tokens per session scan A 4d0c6fe2f658

Subscribe to this mod's changes

AGENTS.quality-testing is an agent published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 295 tokens. 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.