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 saitarrun/Devforge-ai --skill enterprise-test-suitesgit clone --depth 1 https://github.com/saitarrun/Devforge-aiWrote 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/saitarrun/devforge-ai/enterprise-test-suites)<a href="https://agentmods.dev/skills/saitarrun/devforge-ai/enterprise-test-suites"><img src="https://agentmods.dev/badge/skills/saitarrun/devforge-ai/enterprise-test-suites/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/saitarrun/devforge-ai/enterprise-test-suites"><img src="https://agentmods.dev/badge/skills/saitarrun/devforge-ai/enterprise-test-suites.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.00047 | $0.00917 |
| Opus 5.5 | $0.00019 | $0.00367 |
| Sonnet 5.5 | $0.00009 | $0.00183 |
| Haiku 4.5 | $0.00005 | $0.00092 |
Grade A, and why
enterprise-test-suites 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enterprise Multi-Tier Test Suite Engineering Skill
This skill defines industry standards for implementing a resilient, multi-tiered test pyramid for mission-critical enterprise applications.
1. The Enterprise Testing Matrix
/ \
/ \
/ E2E \ → Playwright / Cypress UI workflows
/-------\
/ Contract\ → Pact / OpenAPI Consumer-Provider validation
/-----------\
/ Integration \ → Testcontainers (Postgres, Redis, Kafka)
/---------------\
/ Unit \ → Vitest / Jest / PyTest (>80% branch coverage)
/-------------------\
/ Specialized Suites \
/-----------------------\
• Chaos & Fault Injection (Simulate network drop, latency, node crash)
• Load & Performance (k6 / Artillery latency & concurrency benchmarks)
• Security & Property Fuzzing (Malformed payload injection)
• Mutation Testing (Stryker / mutmut test-quality validation)
2. Test Suite Specifications
A. Unit Test Suite (*.spec.ts / *_test.go)
- Focus: Pure business logic, domain models, mathematical formulas, and validators.
- Rules: Fast (<5ms per test), zero external I/O, deterministic mocking.
- Coverage: Target >80% line and branch coverage.
B. Integration Test Suite (*.integration.spec.ts)
- Focus: Database repositories, ORM queries, cache layers, external API clients, and queue consumers.
- Standard: Use ephemeral real dependencies with Testcontainers (Postgres, Redis, Kafka, LocalStack).
- Invariants: Test database transactions, rollback on failure, connection pools, and migration compatibility.
C. Consumer-Driven Contract Test Suite (*.contract.spec.ts)
- Focus: Microservices API boundaries and webhook contracts.
- Tooling: Pact / MSW.
- Invariants: Assert request/response schemas, error codes, and headers without deploying the full fleet.
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 · 89 lines · 47 tokens per session scan A 6eaa1ae46f72
enterprise-test-suites is a skill published in the GitHub repository saitarrun/Devforge-ai (4 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 917 once invoked, about $0.0002 per session on Opus 5.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-31.
Other skills, from other repositories
proof-strategy
Produce a test strategy for a project or feature — risk map, test type decisions, coverage targets, CI config. Use when asked to "create test strategy", "what should we test", "testing plan", or "improve test coverage".
proof-recon
Testing reconnaissance — inventory all tests, frameworks, coverage, CI integration, and assess testing maturity for project takeover. Use when asked to "understand the tests", "testing assessment", "what's tested", or "test inventory".
sd-test
The disciplined test-recipe gate the generic agent runs for the software-delivery TEST step (/foundry:sd-test, step 8). A PROCEDURE — invoke the MERGED foundry-verify.py executor, read the run record's records whose phase == "testrecipe" (unit / integration / e2e), surface the profile's numeric coveragegate and advise…
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
test-gen
Generate and verify tests — happy path, edge cases, error paths — using the project's own framework and patterns.