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 skills add summarybotng/summarybot-ng --skill enterprise-integration-testinggit clone --depth 1 https://github.com/summarybotng/summarybot-ngWrote 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/skills/summarybotng/summarybot-ng/enterprise-integration-testing)<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/enterprise-integration-testing"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/enterprise-integration-testing/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/skills/summarybotng/summarybot-ng/enterprise-integration-testing"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/enterprise-integration-testing.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.00060 | $0.06836 |
| Opus 5.5 | $0.00024 | $0.02734 |
| Sonnet 5.5 | $0.00012 | $0.01367 |
| Haiku 4.5 | $0.00006 | $0.00684 |
Grade A, and why
enterprise-integration-testing 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 1mo 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
88% identical to enterprise-integration-testing — 8 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 — 736 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enterprise Integration Testing
<default_to_action> When testing enterprise integrations or SAP-connected systems:
- MAP the end-to-end flow (web -> API -> middleware -> backend -> response)
- IDENTIFY integration points and protocols (REST, SOAP, RFC, IDoc, OData, EDI)
- SELECT the right agent for each integration type
- TEST each integration boundary with contract and data validation
- VALIDATE cross-system data consistency (SAP <-> WMS <-> middleware)
- EXERCISE enterprise error handling (compensation, retry, alerting)
- GATE releases with enterprise-specific quality criteria
Agent Selection Guide:
- SAP RFC/BAPI calls ->
qe-sap-rfc-tester - SAP IDoc flows ->
qe-sap-idoc-tester - OData/Fiori services ->
qe-odata-contract-tester - SOAP/ESB endpoints ->
qe-soap-tester - Message broker flows ->
qe-message-broker-tester - Middleware routing/transformation ->
qe-middleware-validator - Authorization / SoD conflicts ->
qe-sod-analyzer
Critical Success Factors:
- Enterprise testing is cross-system: no system is tested in isolation
- Data consistency across systems is the primary quality signal
- Environment access and test data are the biggest bottlenecks </default_to_action>
Quick Reference Card
When to Use
- Testing SAP-connected enterprise systems (S/4HANA, ECC, BW)
- Validating end-to-end business processes (Order-to-Cash, Procure-to-Pay)
- Testing middleware/ESB integrations (IIB, MuleSoft, SAP PI/PO)
- Cross-system data reconciliation (SAP <-> WMS <-> CRM)
- Enterprise release readiness assessment
Enterprise Integration Types
| Integration | Protocol | Agent | Typical Use |
|---|---|---|---|
| SAP RFC/BAPI | RFC | qe-sap-rfc-tester | Real-time SAP function calls |
| SAP IDoc | ALE/EDI | qe-sap-idoc-tester | Asynchronous document exchange |
| SAP OData | REST/OData | qe-odata-contract-tester | Fiori apps, external APIs |
| SOAP/ESB | SOAP/HTTP | qe-soap-tester | Legacy service integration |
| Message Broker | AMQP/JMS | qe-message-broker-tester | Async messaging (MQ, Kafka) |
| Middleware | Various | qe-middleware-validator | Routing, transformation |
| Authorization | SAP Auth | qe-sod-analyzer | SoD conflicts, role testing |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 736 lines · 60 tokens per session scan A c51bf7ad9987
enterprise-integration-testing is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 4mo ago), licensed MIT. It adds 60 tokens to every session and 6,836 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to enterprise-integration-testing, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
enterprise-integration-testing
Use when testing enterprise integrations across SAP, middleware, WMS, or backend systems, validating E2E enterprise flows, testing SAP-specific patterns (RFC, BAPI, IDoc, OData, Fiori), or enforcing cross-system quality gates.
Express.js Testing Patterns
Express.js API testing with supertest, middleware testing, route handler testing, error handling verification, and authentication testing.
erp-integration
Sync orders, inventory, and customer data between your store and ERP systems like SAP, NetSuite, or Odoo using middleware and async queues.
hs-test
Provide executable feedback on changed behavior with the smallest relevant white-box or black-box probe, then classify the result and report real evidence. Diagnose failures against accepted intent, domain rules, and current implementation before deciding whether code, tests, fixtures, or environment are wrong. Use…
scenario-testing
This skill should be used when writing tests, validating features, or needing to verify code works. Triggers on "write tests", "add test coverage", "validate feature", "integration test", "end-to-end", "e2e test", "mock", "unit test". Enforces scenario-driven testing with real dependencies in .scratch/ directory.
integration-testing
Use this skill when testing the full-stack integration between frontend and backend. Covers contract testing and E2E patterns.