run-test-remote

A workflow for sending a test plan to GitHub Actions to run remotely instead of on the local computer. It uses an automated coding agent, reports failures in Microsoft Teams, and publishes an Allure test report to a GitHub Pages branch.

In plain words
What is it for?
Use /Run-test-remote, or an equivalent trigger, to dispatch a test plan to CI, receive failure information in Teams, and view the generated Allure report.
Why use it?
It lets the test run in the project’s cloud workflow and provides failure notifications and a published report.

Skill for Claude CodeCodex

Part of the shesha-auto-testing plugin — 5 skills shipped together

Install

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.

agentmods
npx agentmods add skills/boxfusion/boxfusion-plugins/run-test-remote
Any agent
npx skills add Boxfusion/Boxfusion-plugins --skill run-test-remote
Clone the repo
git clone --depth 1 https://github.com/Boxfusion/Boxfusion-plugins

Made for: Claude Code, Codex.

Or install shesha-auto-testing, the plugin that ships this one along with the rest of its 5 skills.

Per session 241 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,989 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00241 $0.01989
Opus 5 $0.00120 $0.00994
Sonnet 5 $0.00048 $0.00398
Haiku 4.5 $0.00024 $0.00199

Measured 2d ago against content hash 74efa6e4c51b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

run-test-remote 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 2d 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.

plugins/shesha-auto-testing/skills/run-test-remote/SKILL.md · 160 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 2d ago First seen · 160 lines · 241 tokens per session scan A 74efa6e4c51b

Subscribe to this mod's changes

run-test-remote is a skill published in the GitHub repository Boxfusion/Boxfusion-plugins (2 stars, last pushed 20d ago), with no licence file. It adds 241 tokens to every session and 1,989 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-31.

Related

Other skills, from other repositories

deploy-release-test

Validate a commit-specific Next.js preview package and manually trigger the entire Next.js deployment test suite through the teste2edeployrelease.yml GitHub Actions workflow. Use only when asked to run the full deploy test suite or this workflow specifically from an internal vercel/next.js PR branch. Do not use for…

vercel/next.js · 115 tokens

triage-ci-flake

Use when CI tests fail on main branch after PR merge, when investigating flaky test failures, or when user provides a PR URL/number to aggregate all failing tests.

payloadcms/payload · 38 tokens

testing-conventions

Use when adding or changing tests, the e2e harness, test process isolation, or CI test sharding.

kunchenguid/no-mistakes · 27 tokens

running-release-tests

Run automated release testing (UI or API) via the AWS DevOps Agent using a pre-configured test profile. Use when the user wants to validate multi-step workflows, verify features, check for regressions, or test API endpoints. Trigger words include run tests, UAT, test my app, test profile, UI test, API test, automated…

aws/agent-toolkit-for-aws · 91 tokens

playwright-ci

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

zebbern/claude-code-guide · 48 tokens

run-e2e-ci

Trigger the on-demand E2E / Coin Tester CI workflows (Desktop E2E, Mobile E2E, Coin Tester) on a branch and post a PR comment. Use when asked to "run e2e", "trigger e2e on CI", or "run coin testers" for a PR/branch.

LedgerHQ/ledger-live · 71 tokens