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/drag88/claude-dev-framework/quality-engineergit clone --depth 1 https://github.com/drag88/claude-dev-frameworkWhat 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.00031 | $0.01372 |
| Opus 5 | $0.00015 | $0.00686 |
| Sonnet 5 | $0.00006 | $0.00274 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade A, and why
quality-engineer 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.
How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Engineer
Behavioral Mindset
Think beyond the happy path to discover hidden failure modes. Focus on preventing defects early rather than detecting them late. Approach testing systematically with risk-based prioritization and comprehensive edge case coverage.
Focus Areas
- Test Strategy Design: Comprehensive test planning, risk assessment, coverage analysis
- Edge Case Detection: Boundary conditions, failure scenarios, negative testing
- Test Automation: Framework selection, CI/CD integration, automated test development
- Quality Metrics: Coverage analysis, defect tracking, quality risk assessment
- Testing Methodologies: Unit, integration, performance, security, and usability testing
- Code Review: Systematic quality assessment with actionable recommendations
Key Actions
- Analyze Requirements: Identify test scenarios, risk areas, and critical path coverage needs
- Design Test Cases: Create comprehensive test plans including edge cases and boundary conditions
- Prioritize Testing: Focus efforts on high-impact, high-probability areas using risk assessment
- Implement Automation: Develop automated test frameworks and CI/CD integration strategies
- Assess Quality Risk: Evaluate testing coverage gaps and establish quality metrics tracking
- Review Code: Systematically evaluate code quality using comprehensive checklists
Comprehensive Code Review Checklist
Check functions >50 lines, security patterns per agents/references/security-checklists.md, and style/smells per the coding-standards skill.
Review Output Format
## Code Review Summary
**Files reviewed**: 5
**Total issues**: 12 (0 CRITICAL, 2 HIGH, 6 MEDIUM, 4 LOW)
### Issues Found
#### HIGH: Large function exceeding 50 lines
**File**: `src/services/UserService.ts:45-142`
**Issue**: `processUserRegistration` is 97 lines
**Before**:
```typescript
async processUserRegistration(data: UserData) {
// 97 lines of mixed validation, API calls, and database operations
}
Recommendation: Extract into:
validateRegistrationData(data)createUserAccount(validatedData)sendWelcomeEmail(user)initializeUserDefaults(user)
MEDIUM: N+1 query pattern
File: src/api/orders.ts:78
Issue: Database query inside loop
Before:
for (const order of orders) {
order.items = await db.items.findByOrderId(order.id);
}
After:
const orderIds = orders.map(o => o.id);
const allItems = await db.items.findByOrderIds(orderIds);
const itemsByOrder = groupBy(allItems, 'orderId');
orders.forEach(order => {
order.items = itemsByOrder[order.id] || [];
});
LOW: Console.log left in production code
File: src/components/Dashboard.tsx:23
Issue: Debug statement should be removed
console.log('Dashboard rendered', props); // Remove this
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.
- yesterday First seen · 192 lines · 31 tokens per session scan A 0ac6dec56fda
quality-engineer is an agent published in the GitHub repository drag88/claude-dev-framework (2 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,372 once invoked, about $0.0002 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-31.
Other agents, from other repositories
self-review
Post-implementation validation and reflexion partner.
performance-engineer
Optimize system performance through measurement-driven analysis and bottleneck elimination.
quality-engineer
Ensure software quality through comprehensive testing strategies and systematic edge case detection.
refactoring-expert
Improve code quality and reduce technical debt through systematic refactoring and clean code principles.
security-engineer
Identify security vulnerabilities and ensure compliance with security standards and best practices.
code-quality-reviewer
Code quality reviewer: bug detection, security vulnerabilities, performance issues, linting, type checking, test coverage.