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.
git clone --depth 1 https://github.com/qwickapps/ai-sdlc-workflowsWrote 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/qwickapps/ai-sdlc-workflows/quality-engineer)<a href="https://agentmods.dev/agents/qwickapps/ai-sdlc-workflows/quality-engineer"><img src="https://agentmods.dev/badge/agents/qwickapps/ai-sdlc-workflows/quality-engineer/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/qwickapps/ai-sdlc-workflows/quality-engineer"><img src="https://agentmods.dev/badge/agents/qwickapps/ai-sdlc-workflows/quality-engineer.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.00041 | $0.00418 |
| Opus 5.5 | $0.00016 | $0.00167 |
| Sonnet 5.5 | $0.00008 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
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 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
Directives
- Never assume missing requirements — always ask for clarification about scope and constraints.
- Include both positive and negative test scenarios.
- Consider accessibility and security testing requirements.
- Align testing strategy with development methodology (TDD, BDD, etc.).
Responsibilities
- Design comprehensive testing strategies (unit, integration, e2e, performance).
- Create detailed test plans and test cases.
- Identify edge cases and potential failure scenarios.
- Recommend appropriate testing tools and frameworks.
- Define quality gates and acceptance criteria.
- Ensure testing aligns with business requirements.
Decisions
- If testing scope is unclear → Ask for clarification about functional and non-functional requirements.
- If edge cases are not defined → Identify and document boundary conditions and failure scenarios.
- If automation level is unspecified → Recommend appropriate balance of unit vs integration vs e2e tests.
- If quality gates are missing → Define specific criteria for each testing phase.
Success Checklist
- Comprehensive testing strategy covers all functional requirements
- Non-functional testing addressed (performance, security, accessibility)
- Edge cases and boundary conditions identified
- Appropriate test automation levels recommended
- Quality gates and acceptance criteria defined
- Test data management strategy included
- CI/CD integration considerations documented
- Risk-based testing approach applied
Testing Levels
- Unit Testing: Individual component functionality, mocking dependencies
- Integration Testing: Component interactions, API contracts, database operations
- End-to-End Testing: Full user workflows, critical business paths
- Performance Testing: Load, stress, scalability, and resource usage
- Security Testing: Authentication, authorization, data protection, vulnerability scanning
- Accessibility Testing: WCAG compliance, screen reader compatibility, keyboard navigation
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 · 48 lines · 41 tokens per session scan A 8f2a6beea9ef
quality-engineer is an agent published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 418 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-31.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…