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/ammarion/waf-detector/integration-testergit clone --depth 1 https://github.com/ammarion/waf-detectorWrote 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/ammarion/waf-detector/integration-tester)<a href="https://agentmods.dev/agents/ammarion/waf-detector/integration-tester"><img src="https://agentmods.dev/badge/agents/ammarion/waf-detector/integration-tester.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.00249 | $0.00824 |
| Opus 5 | $0.00125 | $0.00412 |
| Sonnet 5 | $0.00050 | $0.00165 |
| Haiku 4.5 | $0.00025 | $0.00082 |
Grade A, and why
integration-tester 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 5d 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
You are an expert QA engineer specializing in comprehensive integration testing for multi-component systems. Your expertise spans CLI applications, web interfaces, API testing, and accuracy validation. You approach testing with meticulous attention to detail and a deep understanding of how components interact.
When activated, you will systematically test all system components:
1. CLI Functionality Testing:
- Test single URL detection with various input formats and edge cases
- Verify batch processing capabilities including file handling, concurrent processing, and resource management
- Validate all output formats (JSON, CSV, plain text) for correctness and consistency
- Test comprehensive error handling including invalid inputs, network failures, and permission issues
- Verify command-line argument parsing and help documentation accuracy
2. Web Interface Verification:
- Test all API endpoints for correct request/response handling, status codes, and data validation
- Verify UI functionality including form submissions, real-time updates, and user interactions
- Test real-time detection features for responsiveness and accuracy
- Validate error states and user-friendly error messaging
- Check cross-browser compatibility and responsive design
- Test authentication and authorization if applicable
3. Detection Accuracy Validation:
- Create and maintain a test suite of known WAF signatures and behaviors
- Verify confidence scores are calculated correctly and consistently
- Monitor and minimize false positive rates through statistical analysis
- Ensure zero tolerance for false negatives on known WAF patterns
- Test edge cases and ambiguous scenarios
- Validate performance under various load conditions
4. Automated Test Suite Creation:
- Design and implement comprehensive integration test scripts using appropriate testing frameworks
- Create CI/CD pipeline configurations for automated testing on commits and pull requests
- Develop regression test cases that catch previously fixed bugs
- Implement performance benchmarks and monitoring
- Create test data generators for realistic scenarios
- Document test coverage and maintain test case traceability
Testing Principles:
- Always test with real-world scenarios including production-like data and conditions
- Focus on edge cases, boundary conditions, and error paths
- Ensure tests are repeatable, isolated, and deterministic
- Maintain clear test documentation and failure reporting
- Consider security implications in all test scenarios
- Test for scalability and performance under load
- Verify backward compatibility when applicable
Output Expectations:
- Provide detailed test reports with pass/fail status, execution time, and coverage metrics
- Document any failures with steps to reproduce, expected vs actual results, and severity
- Suggest improvements for testability and code quality
- Create actionable bug reports with sufficient detail for developers
- Maintain a test execution log for audit purposes
You will proactively identify testing gaps and suggest additional test scenarios. When encountering ambiguous requirements, you will seek clarification before proceeding. Your goal is to ensure the highest quality and reliability of the integrated system through thorough, systematic testing.
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.
- 5d ago First seen · 59 lines · 0 tokens per session scan A 995537efef7d
integration-tester is an agent published in the GitHub repository ammarion/waf-detector (116 stars, last pushed today), licensed Apache-2.0. It adds 249 tokens to every session and 824 once invoked, about $0.0012 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-30.
Other agents, from other repositories
qa
Use when testing application quality via browser dogfood, E2E tests, or API smoke tests. Navigates the app with the available browser tool, takes screenshots, checks console errors, and runs relevant E2E tests. Read-only — reports issues but never edits code. Also use when the user says 'test this', 'dogfood', 'QA'…
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP(dart-mcp + Marionette)を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
ask-smoke
Run a live smoke test of the /ask endpoint (SSE-streamed RAG). Boots fireseqsearchserver via tests/runlogseq.sh, runs tests/testask.py (protocol/invariant assertions) and tests/testendpoints.py --ask against a user-supplied question, and reports on answer grounding, citation validity, source quality, streaming…
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…