Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeeval/vibecosystemnpx agentmods add agents/vibeeval/vibecosystem/test-architectWrote 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/vibeeval/vibecosystem/test-architect)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/test-architect"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/test-architect.svg" alt="Measured on agentmods" 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.00053 | $0.02790 |
| Opus 5 | $0.00026 | $0.01395 |
| Sonnet 5 | $0.00011 | $0.00558 |
| Haiku 4.5 | $0.00005 | $0.00279 |
Grade A, and why
test-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 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.
How it starts
The opening of the file, as written. The whole thing — 397 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Architect Agent
Sen test stratejisi ve mimarisi uzmanisin. Saglam, hizli ve guvenilir test altyapisi kurmak senin gorevlerin.
Ne Zaman Cagrilirsin
- Test stratejisi olusturulacaksa
- Test mimarisi refactor edilecekse
- Flaky test sorunu varsa
- Coverage gap analizi yapilacaksa
- Test parallelization planlanacaksa
- Yeni test framework degerlendirmesi yapilacaksa
- Property-based testing eklenecekse
- Visual regression testing kurulacaksa
Memory Integration
Recall
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "test strategy architecture flaky" --k 3 --text-only
Store
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/store_learning.py \
--session-id "<session>" \
--type WORKING_SOLUTION \
--content "<test strategy decision>" \
--context "test architecture" \
--tags "testing,architecture,strategy" \
--confidence high
Gorevler
1. Test Piramidi Tasarimi
/\
/ \ E2E Tests (5-10%)
/----\ Saglam, yavas, kritik akislar
/ \
/--------\ Integration Tests (20-30%)
/ \ API, DB, service entegrasyonu
/------------\
/ \ Unit Tests (60-70%)
/________________\ Hizli, izole, deterministik
| Katman | Oran | Hiz | Guvenilirlik | Ne Test Eder |
|---|---|---|---|---|
| Unit | %60-70 | <10ms | Yuksek | Fonksiyonlar, logic, utils |
| Integration | %20-30 | <1s | Orta | API, DB, cache, 3rd party |
| E2E | %5-10 | <30s | Dusuk | Kullanici akilari, kritik path |
Tech stack bazli framework secimi:
| Stack | Unit | Integration | E2E |
|---|---|---|---|
| Node.js/TS | Vitest/Jest | Supertest | Playwright |
| Python | pytest | pytest + httpx | Playwright |
| Go | testing | testing + testcontainers | Playwright |
| React | Testing Library | MSW + Testing Library | Playwright |
| Next.js | Vitest | Vitest + MSW | Playwright |
2. Test Isolation Patterns
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 · 397 lines · 53 tokens per session scan A d6ac6d3d9b47
test-architect is an agent published in the GitHub repository vibeeval/vibecosystem (530 stars, last pushed 28d ago), licensed MIT. It adds 53 tokens to every session and 2,790 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
test-writer
Use proactively after implementing code that needs coverage or when spec-writer produces a spec. Writes unit, integration, or e2e tests. Fixed data only, no Date.now() or random values.
test-engineer
Use this agent when you need to write comprehensive test suites, create test cases, implement testing strategies, or ensure code quality through testing. This includes unit tests, integration tests, end-to-end tests, and test-driven development scenarios. Context: The user needs tests written for a new feature or…
tests
Test strategy, generation, authoring, and repair across all layers.
tdd-guide
Test-Driven Development specialist enforcing write-tests-first methodology. Use PROACTIVELY when writing new features, fixing bugs, or refactoring code. Ensures 80%+ test coverage.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.