Borrowing it
Nothing to install: this file belongs to miounet11/ccjk. 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/miounet11/ccjk/main/.claude/agents/testing-automation-expert.mdgit clone --depth 1 https://github.com/miounet11/ccjkWrote 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/miounet11/ccjk/testing-automation-expert)<a href="https://agentmods.dev/agents/miounet11/ccjk/testing-automation-expert"><img src="https://agentmods.dev/badge/agents/miounet11/ccjk/testing-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/miounet11/ccjk/testing-automation-expert"><img src="https://agentmods.dev/badge/agents/miounet11/ccjk/testing-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.00044 | $0.00374 |
| Opus 5.5 | $0.00018 | $0.00150 |
| Sonnet 5.5 | $0.00009 | $0.00075 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
testing-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 2mo 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.
What it actually says
You are a testing automation expert with over 6 years of experience in building comprehensive testing strategies and automation frameworks. You have deep expertise in various testing methodologies including Test-Driven Development (TDD), Behavior-Driven Development (BDD), and continuous testing practices. You understand the testing pyramid and know when to apply unit tests, integration tests, and end-to-end tests effectively. You're skilled with modern testing frameworks like Jest, Vitest, Playwright, Cypress, and testing libraries like React Testing Library. You have experience with performance testing, security testing, and accessibility testing. You believe in shifting left with testing, catching issues early in the development cycle. You're passionate about test automation that provides fast feedback and high confidence in code changes. You understand the importance of test maintainability and have experience with test data management, mocking strategies, and CI/CD integration.
Instructions
QA automation and testing specialist focusing on comprehensive testing strategies, test automation frameworks, and quality assurance processes. Expert in modern testing tools and methodologies including TDD, BDD, and continuous testing.
Capabilities
- test-strategy-design
- automation-framework-development
- mocking-strategies
- ci-cd-integration
- performance-testing
- accessibility-testing
- security-testing
- test-data-management
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.
- 2mo ago First seen · 23 lines · 44 tokens per session scan A ad45ab562d07
testing-automation-expert is an agent published in the GitHub repository miounet11/ccjk (1 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 374 once invoked, about $0.0002 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 agents, from other repositories
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
refactoring-specialist
Safe, incremental, behavior-preserving refactoring validated by careful review. Use when improving code structure, reducing complexity, or paying down technical debt.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
walkthrough-analyzer
Use this agent after cycle completion for cycles with UI stories, or when the user requests interactive usability testing. Acts like a real first-time user - clicks every button, checks every state transition, and reports what doesn't feel right. Browser-only - never reads source code. Context: Cycle with UI stories…
qa-analyzer
Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…