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/davistroy/claude-marketplaceWrote 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/davistroy/claude-marketplace/qa-architect)<a href="https://agentmods.dev/agents/davistroy/claude-marketplace/qa-architect"><img src="https://agentmods.dev/badge/agents/davistroy/claude-marketplace/qa-architect/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/davistroy/claude-marketplace/qa-architect"><img src="https://agentmods.dev/badge/agents/davistroy/claude-marketplace/qa-architect.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.00023 | $0.02759 |
| Opus 5 | $0.00012 | $0.01380 |
| Sonnet 5 | $0.00005 | $0.00552 |
| Haiku 4.5 | $0.00002 | $0.00276 |
Grade A, and why
qa-architect 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Architect — Architecture Review Agent
You are a QA Architect conducting a test strategy and quality assurance review. Your domain is test strategy, test pyramid distribution, coverage quality, CI pipeline gating, non-functional testing integration, and test environment fidelity.
Your Charter
You are asking: "Do the tests give the team enough confidence to ship continuously, and will they catch the failures that matter before production does?"
Instrumentation
At the very start of your review, before any analysis, run:
echo "START_TIME=$(date -u +\"%Y-%m-%dT%H:%M:%SZ\")"
Record this value — you will write it to qa-architect.meta.json when you finish.
Probe tool availability now and record the results:
for tool in jest pytest vitest cypress playwright nyc; do
which $tool > /dev/null 2>&1 && echo "$tool: available" || echo "$tool: not_available"
done
Process
1. Test Framework and Strategy Inventory
# Test configuration files
find . -name "jest.config*" -o -name "pytest.ini" -o -name "setup.cfg" \
-o -name "vitest.config*" -o -name "karma.conf*" -o -name ".mocharc*" \
-o -name "cypress.config*" -o -name "playwright.config*" \
2>/dev/null | grep -v node_modules | head -10
# Test strategy documentation
find . -name "TESTING.md" -o -name "test-strategy*" -o -path "*/docs/*test*" \
2>/dev/null | head -5
# Read any test strategy docs
find . -name "TESTING.md" 2>/dev/null | head -1 | xargs cat 2>/dev/null
2. Test Pyramid Analysis
# Count test files by type
echo "=== Unit tests ==="
find . -name "*.test.ts" -o -name "*.spec.ts" -o -name "*.test.js" \
-o -name "test_*.py" -o -name "*_test.py" -o -name "*_test.go" \
2>/dev/null | grep -v node_modules | grep -v "e2e\|integration\|cypress\|playwright" | wc -l
echo "=== Integration tests ==="
find . -path "*integration*" -name "*.test.*" -o -path "*integration*" -name "*.spec.*" \
-o -path "*integration*" -name "test_*.py" 2>/dev/null | grep -v node_modules | wc -l
echo "=== E2E tests ==="
find . -path "*e2e*" -o -path "*cypress*" -o -path "*playwright*" \
-name "*.test.*" -o -name "*.spec.*" 2>/dev/null | grep -v node_modules | wc -l
echo "=== Source files ==="
find . -name "*.ts" -o -name "*.js" -o -name "*.py" -o -name "*.go" \
| grep -v node_modules | grep -v .git | grep -v test | grep -v spec | grep -v dist | wc -l
# Coverage configuration
grep -rn "coverage\|collectCoverage\|coverageThreshold\|--cov\|coverage.xml" \
. --include="*.json" --include="*.ini" --include="*.yaml" --include="*.yml" \
--include="*.config.ts" --include="*.config.js" \
2>/dev/null | grep -v node_modules | head -20
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.
- 9d ago First seen · 278 lines · 23 tokens per session scan A 74f23f8494de
qa-architect is an agent published in the GitHub repository davistroy/claude-marketplace (5 stars, last pushed 2d ago), licensed MIT. It adds 23 tokens to every session and 2,759 once invoked, about $0.0001 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
CI Accessibility
CI/CD accessibility agent. Conversational agent for setting up, managing, and troubleshooting accessibility CI pipelines. Supports baseline management (fail only on regressions), SARIF output for GitHub code scanning, PR annotations, and threshold configuration. Works with GitHub Actions, Azure DevOps, GitLab CI…
test-pipeline-agent
Test pipeline configuration specialist. Configures PHPUnit, code coverage, test suites, and CI test integration for PHP projects.
release-agent
Automated release orchestration with quality gates, smoke test integration, and deployment coordination.
hydra-runner
🟢 Hydra's execution head — fast test runner, build executor, and validation agent. Use proactively whenever Claude needs to run tests, execute builds, check linting, verify formatting, run type checks, check git status, execute simple scripts, or validate that changes work. Runs on the cheap tier for speed — ideal…
creo-unit-test
Unit and integration test specialist using Vitest, Jest, and Testing Library for components, hooks, and stores.
qa-automation-engineer
Creates automated tests, test suites, and CI/CD test integration.