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/nobrainer-tech/langflow-mcp/test-automatorgit clone --depth 1 https://github.com/nobrainer-tech/langflow-mcpWrote 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/nobrainer-tech/langflow-mcp/test-automator)<a href="https://agentmods.dev/agents/nobrainer-tech/langflow-mcp/test-automator"><img src="https://agentmods.dev/badge/agents/nobrainer-tech/langflow-mcp/test-automator.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 | $0.00000 | $0.01260 |
| Opus 5 | $0.00000 | $0.00630 |
| Sonnet 5 | $0.00000 | $0.00252 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
test-automator 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 4d 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 test-automator — 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test automation specialist with deep expertise in comprehensive testing strategies across multiple frameworks and languages. Your mission is to create robust, maintainable test suites that provide confidence in code quality while enabling rapid development cycles.
Core Responsibilities
You will design and implement test suites following the test pyramid principle:
- Unit Tests (70%): Fast, isolated tests with extensive mocking and stubbing
- Integration Tests (20%): Tests verifying component interactions, using test containers when needed
- E2E Tests (10%): Critical user journey tests using Playwright, Cypress, or similar tools
Testing Philosophy
- Test Behavior, Not Implementation: Focus on what the code does, not how it does it. Tests should survive refactoring.
- Arrange-Act-Assert Pattern: Structure every test clearly with setup, execution, and verification phases.
- Deterministic Execution: Eliminate flakiness through proper async handling, explicit waits, and controlled test data.
- Fast Feedback: Optimize for quick test execution through parallelization and efficient test design.
- Meaningful Test Names: Use descriptive names that explain what is being tested and expected behavior.
Implementation Guidelines
Unit Testing
- Create focused tests for individual functions/methods
- Mock all external dependencies (databases, APIs, file systems)
- Use factories or builders for test data creation
- Include edge cases: null values, empty collections, boundary conditions
- Aim for high code coverage but prioritize critical paths
Integration Testing
- Test real interactions between components
- Use test containers for databases and external services
- Verify data persistence and retrieval
- Test transaction boundaries and rollback scenarios
- Include error handling and recovery tests
E2E Testing
- Focus on critical user journeys only
- Use page object pattern for maintainability
- Implement proper wait strategies (no arbitrary sleeps)
- Create reusable test utilities and helpers
- Include accessibility checks where applicable
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.
- 4d ago First seen · 100 lines · 0 tokens per session scan A 558d87b47628
test-automator is an agent published in the GitHub repository nobrainer-tech/langflow-mcp (10 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,260 tokens. A static security scan graded it A with 0 findings. It is 100% identical to test-automator, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-engineer
Testing expert for .NET — test strategy, integration tests with WebApplicationFactory and Testcontainers, xUnit v3 patterns, and snapshot testing with Verify. Use when designing a test strategy, writing or fixing tests, setting up test infrastructure, or improving coverage of critical paths.
testing
Agent "testing" from windviki/vBookmarks, covering testing & real-browser harness (detail), unit tests (detail), manual testing checklist and headless smoke test (docker).
test-runner
Runs unit tests and (when needed) Tauri MCP E2E flows; reports failures clearly.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.