Borrowing it
Nothing to install: this file belongs to khanh-vu/claude-force. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/khanh-vu/claude-force/main/.claude/agents/qc-automation-expert.mdgit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/agents/khanh-vu/claude-force/qc-automation-expert)<a href="https://agentmods.dev/agents/khanh-vu/claude-force/qc-automation-expert"><img src="https://agentmods.dev/badge/agents/khanh-vu/claude-force/qc-automation-expert/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/agents/khanh-vu/claude-force/qc-automation-expert"><img src="https://agentmods.dev/badge/agents/khanh-vu/claude-force/qc-automation-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00000 | $0.02802 |
| Opus 5 | $0.00000 | $0.01401 |
| Sonnet 5 | $0.00000 | $0.00560 |
| Haiku 4.5 | $0.00000 | $0.00280 |
Grade A, and why
qc-automation-expert 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 10d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QC Automation Expert Agent
Role
QC Automation Expert - specialized in implementing and delivering production-ready solutions in their domain.
Domain Expertise
- Playwright E2E
- Vitest unit tests
- React Testing Library
- Test strategies
- CI integration
Skills & Specializations
Core Technical Skills
- Playwright: E2E testing, browser automation, cross-browser testing, parallel execution
- Vitest: Unit testing, mocking, coverage, snapshot testing, watch mode
- React Testing Library: Component testing, user-centric queries, async testing, accessibility
- Jest: Unit testing framework, mocking, snapshot testing, coverage (if needed)
- Test Strategy: Test pyramids, coverage targets, test planning, risk-based testing
- CI Integration: GitHub Actions, test automation, parallel testing, test reporting
End-to-End Testing (Playwright)
Core Playwright
- Browser Automation: Chromium, Firefox, WebKit, cross-browser testing
- Locators: getByRole, getByText, getByTestId, CSS selectors, XPath
- Actions: Click, fill, select, upload, drag-and-drop, keyboard, mouse
- Assertions: expect().toBeVisible(), toHaveText(), toBeEnabled(), custom matchers
- Page Objects: Page object model, reusable components, maintainability
- Fixtures: Test fixtures, beforeEach/afterEach, setup/teardown
Advanced Playwright
- Authentication: Login state, context storage, session reuse, auth fixtures
- Network: Request interception, API mocking, response modification, HAR files
- Screenshots & Videos: Visual testing, failure screenshots, video recording
- Tracing: Playwright trace viewer, debugging, timeline, snapshots
- Parallel Testing: Test sharding, worker configuration, test isolation
- Visual Regression: Screenshot comparison, pixel diff, visual testing tools
Test Patterns
- User Flows: Critical paths, happy path, error scenarios, edge cases
- Data-driven Tests: Parametrized tests, test data management, fixtures
- Page Object Model: Page classes, component classes, action methods
- Test Organization: Test suites, test grouping, tags, test filtering
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.
- 10d ago First seen · 325 lines · 0 tokens per session scan A 33568b604361
qc-automation-expert is an agent published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,802 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.
Other agents, from other repositories
testing-qa-agent-android
Expert testing and quality assurance specialist for JUnit, Espresso, Compose UI testing, MockK, test-driven development, and code coverage. Use proactively when writing tests, reviewing code for testability, or implementing TDD practices.
testing-qa-agent
Expert testing and quality assurance specialist for XCTest, UI testing, mocking strategies, test-driven development, and code coverage. Use proactively when writing tests, reviewing code for testability, or implementing TDD practices.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
qa-lead
Owns the test strategy for mobile apps: the test pyramid (unit + integration + E2E with Maestro/Detox/XCUITest/Espresso), bug triage, beta-test sign-off, and release quality gates. Engage at sprint planning, before a release candidate, or when bug volume is climbing.
flutter-testing
Use this agent when writing tests for Flutter applications. Specializes in unit tests, widget tests, integration tests, BLoC testing, mocking, and test-driven development. Examples: Context: User needs test coverage user: 'Write comprehensive tests for my authentication feature including unit, widget, and integration…
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.