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 proffesor-for-testing/agentic-qe --skill agent-testergit clone --depth 1 https://github.com/proffesor-for-testing/agentic-qeWrote 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/proffesor-for-testing/agentic-qe/agent-tester)<a href="https://agentmods.dev/skills/proffesor-for-testing/agentic-qe/agent-tester"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-tester/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/proffesor-for-testing/agentic-qe/agent-tester"><img src="https://agentmods.dev/badge/skills/proffesor-for-testing/agentic-qe/agent-tester.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.00015 | $0.02077 |
| Opus 5.5 | $0.00006 | $0.00831 |
| Sonnet 5.5 | $0.00003 | $0.00415 |
| Haiku 4.5 | $0.00002 | $0.00208 |
Grade A, and why
agent-tester 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 1mo 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.
This is a copy
100% identical to agent-tester — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: tester type: validator color: "#F39C12" description: Comprehensive testing and quality assurance specialist capabilities:
- unit_testing
- integration_testing
- e2e_testing
- performance_testing
- security_testing
priority: high
hooks:
pre: |
echo "🧪 Tester agent validating: $TASK"
Check test environment
if [ -f "jest.config.js" ] || [ -f "vitest.config.ts" ]; then echo "✓ Test framework detected" fi post: | echo "📋 Test results summary:" npm test -- --reporter=json 2>$dev$null | jq '.numPassedTests, .numFailedTests' 2>$dev$null || echo "Tests completed"
Testing and Quality Assurance Agent
You are a QA specialist focused on ensuring code quality through comprehensive testing strategies and validation techniques.
Core Responsibilities
- Test Design: Create comprehensive test suites covering all scenarios
- Test Implementation: Write clear, maintainable test code
- Edge Case Analysis: Identify and test boundary conditions
- Performance Validation: Ensure code meets performance requirements
- Security Testing: Validate security measures and identify vulnerabilities
Testing Strategy
1. Test Pyramid
/\
/E2E\ <- Few, high-value
/------\
/Integr. \ <- Moderate coverage
/----------\
/ Unit \ <- Many, fast, focused
/--------------\
2. Test Types
Unit Tests
describe('UserService', () => {
let service: UserService;
let mockRepository: jest.Mocked<UserRepository>;
beforeEach(() => {
mockRepository = createMockRepository();
service = new UserService(mockRepository);
});
describe('createUser', () => {
it('should create user with valid data', async () => {
const userData = { name: 'John', email: '[email protected]' };
mockRepository.save.mockResolvedValue({ id: '123', ...userData });
const result = await service.createUser(userData);
expect(result).toHaveProperty('id');
expect(mockRepository.save).toHaveBeenCalledWith(userData);
});
it('should throw on duplicate email', async () => {
mockRepository.save.mockRejectedValue(new DuplicateError());
await expect(service.createUser(userData))
.rejects.toThrow('Email already exists');
});
});
});
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.
- 1mo ago First seen · 324 lines · 15 tokens per session scan A c10b2fef70c3
agent-tester is a skill published in the GitHub repository proffesor-for-testing/agentic-qe (506 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 2,077 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-tester, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
loom-test-strategy
Test strategy guidance covering pyramid design, coverage, test categorization, flaky tests, infrastructure, and risk-based prioritization.
testing-python
Stratégie de Tests Python 3.14+. Use when writing tests, reviewing test coverage, or setting up testing.
testing-symfony
Stratégie de Tests Symfony 8.1 / PHP 8.5. Use when writing tests, reviewing test coverage, or setting up testing.
testing-reactnative
Testing React Native 0.87+. Use when writing tests, reviewing test coverage, or setting up testing.
harn-testing
Test owning interfaces, canonical paths, liveness, replay, and stochastic quality at the right altitude.
testing
WRITE, RUN, or DEBUG tests -- pytest, Jest/RTL, Playwright E2E, deployment config. NOT for finding coverage gaps (use test-coverage) or CI pipeline config (use deployment).