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 jnPiyush/AgentX --skill test-automationgit clone --depth 1 https://github.com/jnPiyush/AgentXWrote 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/jnpiyush/agentx/test-automation)<a href="https://agentmods.dev/skills/jnpiyush/agentx/test-automation"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/test-automation/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/jnpiyush/agentx/test-automation"><img src="https://agentmods.dev/badge/skills/jnpiyush/agentx/test-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 134 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 135 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 137 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 241 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00043 | $0.02473 |
| Opus 5.5 | $0.00017 | $0.00989 |
| Sonnet 5.5 | $0.00009 | $0.00495 |
| Haiku 4.5 | $0.00004 | $0.00247 |
Grade A, and why
test-automation 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Automation
Purpose: Build robust automated test infrastructure for continuous, reliable, and fast testing. Scope: Framework setup, CI integration, parallel execution, test data, reporting, environment management.
When to Use This Skill
- Setting up a new test framework for a project
- Configuring CI/CD pipelines for automated testing
- Implementing parallel test execution for speed
- Building test data factories and fixtures
- Creating test reporting dashboards
- Managing test environments (provisioning, teardown)
- Optimizing slow test suites
When NOT to Use
- Writing specific test cases for a feature (use e2e/integration/unit testing skills)
- Performance benchmarking (use performance testing)
- Security scanning (use security testing)
Prerequisites
- Source code repository with CI/CD pipeline
- Test framework selected for the tech stack
- Test environment available (or infrastructure-as-code)
Decision Tree
What test automation task?
+- New project setup?
| +- Which stack?
| | +- TypeScript/JS -> Jest or Vitest (unit) + Playwright (e2e)
| | +- Python -> pytest + playwright-python
| | +- C#/.NET -> xUnit + Playwright for .NET
| | +- Java -> JUnit 5 + Selenium/Playwright
| | +- Go -> testing package + testify
+- CI pipeline integration?
| +- GitHub Actions -> .github/workflows/test.yml
| +- Azure Pipelines -> azure-pipelines.yml
| +- GitLab CI -> .gitlab-ci.yml
+- Tests too slow?
| +- Parallelize across workers/shards
| +- Use test impact analysis (only run affected)
| +- Cache dependencies and build artifacts
+- Test data management?
| +- Factories for dynamic data generation
| +- Fixtures for static seed data
| +- Database snapshots for integration tests
+- Flaky tests?
| +- Quarantine, investigate, and fix
| +- Add retry with reporting (not silent retry)
+- Test reporting?
| +- JUnit XML for CI integration
| +- HTML reports for human review
| +- Coverage reports with thresholds
Framework Selection Guide
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 · 325 lines · 43 tokens per session scan A 4355bf2f642a
test-automation is a skill published in the GitHub repository jnPiyush/AgentX (16 stars, last pushed 3d ago), licensed Apache-2.0. It adds 43 tokens to every session and 2,473 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-09-03.
Other skills, from other repositories
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
quality-scan
Run a scoped, read-only quality scan and report exact-candidate evidence, failures and frozen debt. Use for an ad-hoc gate sweep or release preparation; a static scan is not full release acceptance.
e2e-testing
Use when reviewing CI coverage, automated checks, or test strategy related to Implement end-to-end testing. Focus on whether the rule is continuously verified, not just documented.
mirrord-prev-env
Help users create and manage mirrord preview environments — running a modified service as an isolated pod in a shared Kubernetes cluster, scoped by an environment key and HTTP/queue traffic filtering, so teams can validate and review changes against real traffic without affecting live services. Use when a developer…
ci
Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…
test-setup
Scaffold the test framework and CI — tests/ directory, engine test runner, GitHub Actions workflow. Once, before the first sprint.