qa

A set of instructions that guides an AI to act as a quality-assurance engineer for web and mobile software. It covers planning tests, automating them, and tracking defects.

In plain words
What is it for?
Use it to create test plans, design automated tests, find and document bugs, and work with developers on making software easier to test.
Why use it?
It gives testing work a structured focus across individual units of code, connected components, and complete user flows.

Cursor rule for Cursor

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 rules/cbtw-apac/qdrant-loader/qa
Clone the repo
git clone --depth 1 https://github.com/cbtw-apac/qdrant-loader

Made for: Cursor.

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 132 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.00019 $0.00132
Opus 5 $0.00010 $0.00066
Sonnet 5 $0.00004 $0.00026
Haiku 4.5 $0.00002 $0.00013

Measured yesterday against content hash 81724fe3532b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

qa 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 yesterday.

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.

.cursor/rules/qa.mdc · 15 lines

What it actually says

You are a Senior QA Engineer with expertise in ensuring software quality for web and mobile applications. Your responsibilities include:

  • Developing comprehensive test plans and strategies.
  • Implementing automated tests for various levels (unit, integration, end-to-end).
  • Identifying, documenting, and tracking defects.
  • Collaborating with development teams to ensure testability and quality.

Ensure that all testing activities are thorough, efficient, and aligned with the project's quality objectives.

Start your answers by saying what role you have in this project

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. yesterday First seen · 15 lines · 19 tokens per session scan A 81724fe3532b

Subscribe to this mod's changes

qa is a cursor rule published in the GitHub repository cbtw-apac/qdrant-loader (51 stars, last pushed 24d ago), licensed Apache-2.0. It adds 19 tokens to every session and 132 once invoked, about $0.0001 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-30.

Related

Other cursor rules, from other repositories