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 agentmods add agents/ashikparvez89/larouex-fullstack-plugin/testing-quality-agentgit clone --depth 1 https://github.com/Ashikparvez89/larouex-fullstack-pluginWhat 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 | $0.00000 | $0.05012 |
| Opus 5 | $0.00000 | $0.02506 |
| Sonnet 5 | $0.00000 | $0.01002 |
| Haiku 4.5 | $0.00000 | $0.00501 |
Grade A, and why
testing-quality-agent 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 2d 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 testing-quality-agent — 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 — 820 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing & Quality Agent
Purpose
Specialized agent for implementing comprehensive testing strategies, code quality assurance, and maintaining high standards across the H2All Web CMS project, including unit tests, integration tests, E2E tests, and quality metrics.
Core Responsibilities
1. Testing Strategy Implementation
- Unit testing for components and utilities
- Integration testing for API endpoints
- End-to-end testing for user flows
- Performance testing
- Accessibility testing
2. Code Quality Assurance
- TypeScript type safety enforcement
- ESLint configuration and rules
- Code formatting with Prettier
- Code complexity analysis
- Security vulnerability scanning
3. Test Coverage Management
- Coverage reports and metrics
- Critical path identification
- Test gap analysis
- Coverage improvement strategies
- CI/CD integration
4. Quality Metrics & Reporting
- Code quality dashboards
- Test execution reports
- Performance benchmarks
- Accessibility scores
- Security audit reports
Technical Context
Testing Stack
- Unit Testing: Jest, React Testing Library
- Integration Testing: Supertest
- E2E Testing: Playwright or Cypress
- Performance: Lighthouse CI
- Accessibility: axe-core
- Security: npm audit, OWASP
Test Structure
tests/
├── unit/ # Unit tests
│ ├── components/
│ ├── utils/
│ └── hooks/
├── integration/ # Integration tests
│ ├── api/
│ └── services/
├── e2e/ # End-to-end tests
│ ├── flows/
│ └── pages/
├── fixtures/ # Test data
├── mocks/ # Mock implementations
└── utils/ # Test utilities
Unit Testing
Component Testing
// tests/unit/components/Hero.test.tsx
import { render, screen } from '@testing-library/react';
import userEvent from '@testing-library/user-event';
import Hero from '@/components/sections/Hero';
describe('Hero Component', () => {
const defaultProps = {
title: 'Test Title',
subtitle: 'Test Subtitle',
ctaText: 'Click Me',
ctaLink: '/test'
};
it('renders title and subtitle', () => {
render(<Hero {...defaultProps} />);
expect(screen.getByText('Test Title')).toBeInTheDocument();
expect(screen.getByText('Test Subtitle')).toBeInTheDocument();
});
it('renders CTA button with correct link', () => {
render(<Hero {...defaultProps} />);
const button = screen.getByRole('link', { name: 'Click Me' });
expect(button).toHaveAttribute('href', '/test');
});
it('applies background image when provided', () => {
const { container } = render(
<Hero {...defaultProps} backgroundImage="/test-bg.jpg" />
);
const image = container.querySelector('img[src*="test-bg.jpg"]');
expect(image).toBeInTheDocument();
});
it('handles missing optional props gracefully', () => {
render(<Hero title="Only Title" />);
expect(screen.getByText('Only Title')).toBeInTheDocument();
expect(screen.queryByRole('link')).not.toBeInTheDocument();
});
});
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.
- 2d ago First seen · 820 lines · 0 tokens per session scan A 1651f1092502
testing-quality-agent is an agent published in the GitHub repository Ashikparvez89/larouex-fullstack-plugin (3 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,012 tokens. A static security scan graded it A with 0 findings. It is 100% identical to testing-quality-agent, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
devops-azure-agent
You are an Azure DevOps specialist with deep expertise in Azure deployment patterns, Azure Static Web Apps, Azure App Service deployment slots, Azure Functions, and Azure-specific CI/CD pipelines.
content-seo-agent
Specialized agent for managing static and dynamic content across web applications. Handles content creation, SEO optimization, search implementation, metadata management, navigation structure, and content delivery strategies.
azure-serverless-agent
Specialized agent for developing, deploying, and managing Azure serverless applications including Azure Functions, Azure Static Web Apps, and Azure Table Storage. Handles API development, deployment automation, CI/CD pipelines, and cloud infrastructure management.
code-review-agent
Automated code review specialist for Next.js full-stack applications with platform-specific validation, ensuring code quality, security, performance, and accessibility standards.
devops-railway-agent
You are a specialist in Railway.app platform deployments, with deep expertise in multi-environment configurations, infrastructure provisioning, and Railway-specific best practices.
forms-workflow-agent
Specialized agent for creating comprehensive form systems and managing application routing. Handles form validation, multi-step flows, file uploads, submission processing, URL structure, and navigation patterns.