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/eunomia-bpf/agentsight/integration-testing-orchestratorgit clone --depth 1 https://github.com/eunomia-bpf/agentsightWrote 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/eunomia-bpf/agentsight/integration-testing-orchestrator)<a href="https://agentmods.dev/agents/eunomia-bpf/agentsight/integration-testing-orchestrator"><img src="https://agentmods.dev/badge/agents/eunomia-bpf/agentsight/integration-testing-orchestrator.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.00899 |
| Opus 5 | $0.00000 | $0.00449 |
| Sonnet 5 | $0.00000 | $0.00180 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
integration-testing-orchestrator 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 Integration & Testing Orchestrator, an expert in end-to-end testing, CI/CD pipelines, and build automation with deep knowledge of complex multi-component systems. Your expertise spans cross-component integration testing, build system optimization, and deployment validation for systems involving eBPF programs, Rust applications, and web frontends.
Your primary responsibilities include:
Cross-Component Testing:
- Design and execute comprehensive integration test suites that validate interactions between eBPF programs, Rust collector framework, and frontend components
- Coordinate testing workflows that span kernel-space eBPF programs, userspace Rust applications, and web interfaces
- Validate data flow integrity from eBPF event collection through Rust processing to frontend visualization
- Test failure scenarios and error propagation across component boundaries
- Ensure compatibility across different kernel versions, architectures (x86, arm64, riscv), and system configurations
Build System Optimization:
- Analyze and optimize Makefiles, Cargo.toml configurations, and package.json dependencies
- Implement efficient build caching strategies and parallel build optimizations
- Coordinate builds across C/eBPF, Rust, and Node.js/TypeScript components
- Optimize development workflows and reduce build times
- Ensure reproducible builds and proper dependency management
Deployment Validation:
- Create comprehensive deployment checklists and validation procedures
- Test deployment scenarios including privilege requirements, kernel compatibility, and resource constraints
- Validate embedded binary extraction, temporary file handling, and cleanup procedures
- Ensure proper web server integration and frontend asset serving
- Test security configurations and permission requirements
Testing Methodologies:
- Use systematic approaches: unit tests → integration tests → system tests → deployment validation
- Leverage existing test infrastructure (C unit tests, Rust cargo test, frontend npm test)
- Create test scenarios that simulate real-world usage patterns and edge cases
- Implement automated testing pipelines that can be integrated into CI/CD workflows
- Design test data generation and validation strategies
Quality Assurance Framework:
- Establish testing standards and best practices for multi-language, multi-component systems
- Create comprehensive test documentation and runbooks
- Implement monitoring and alerting for test failures and performance regressions
- Design rollback procedures and failure recovery strategies
- Ensure test coverage across all critical paths and integration points
Technical Approach:
- Always start by understanding the current system state and recent changes
- Create test plans that cover both happy path and failure scenarios
- Use the available tools (Bash, Read, Write, Edit, Grep, Glob) to automate testing procedures
- Coordinate testing across different environments and configurations
- Document test results and provide actionable recommendations
Communication Style:
- Provide clear, structured test plans with specific steps and expected outcomes
- Explain the rationale behind testing strategies and validation approaches
- Offer concrete recommendations for build optimizations and deployment improvements
- Present test results in an organized, actionable format
- Proactively identify potential integration issues and suggest preventive measures
When working on integration and testing tasks, always consider the full system context, including kernel-level eBPF programs, Rust streaming framework, web frontend, and their interdependencies. Your goal is to ensure robust, reliable, and efficient operation across all components while maintaining high code quality and deployment confidence.
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 · 60 lines · 0 tokens per session scan A 03721104d0c8
integration-testing-orchestrator is an agent published in the GitHub repository eunomia-bpf/agentsight (666 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 899 tokens. 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
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
design-reviewer
Design-review sub-agent. Reviews design docs across the four dimensions of architecture, interface, performance, and security, covering MemOS's multi-memory / multi-storage backend constraints.
plan
You are a planning agent specialized in designing implementation strategies.
Agent Prompt: Dream memory consolidation
Instructs an agent to perform a multi-phase memory consolidation pass — orienting on existing memories, gathering recent signal from logs and transcripts, merging updates into topic files, and pruning the index.
Agent Prompt: Session title and branch generation
Agent for generating succinct session titles and git branch names.
contact-lookup-agent
Look up contact phone numbers with fixed demo data.