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 LambdaTest/agent-skills --skill hyperexecute-skillgit clone --depth 1 https://github.com/LambdaTest/agent-skillsWrote 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/lambdatest/agent-skills/hyperexecute-skill)<a href="https://agentmods.dev/skills/lambdatest/agent-skills/hyperexecute-skill"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/hyperexecute-skill/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/lambdatest/agent-skills/hyperexecute-skill"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/hyperexecute-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00097 | $0.00810 |
| Opus 5 | $0.00048 | $0.00405 |
| Sonnet 5 | $0.00019 | $0.00162 |
| Haiku 4.5 | $0.00010 | $0.00081 |
Grade A, and why
hyperexecute-skill 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 10d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HyperExecute Operator
Quick Start
- Locate the HyperExecute CLI. If missing, ask before downloading it unless the user explicitly approved an autonomous HyperExecute session.
- Run
hyperexecute analyzewhen the CLI is available; use local inspection only as fallback. - Create or repair
hyperexecute.yamlfrom the analyze output, project test commands, and templates inreference/. - Run
node scripts/doctor.js --config hyperexecute.yamlandnode scripts/validate-config.js hyperexecute.yaml. - Validate with the official CLI:
./hyperexecute --user "$LT_USERNAME" --key "$LT_ACCESS_KEY" --config hyperexecute.yaml --validate. - Ask before a real cloud job unless the user has explicitly opted into an autonomous HyperExecute session.
- For failures, download logs/artifacts/reports and use
reference/troubleshooting.md.
Operating Rules
- Treat the official HyperExecute CLI as the source of truth for analyze, validation, execution, logs, reports, and artifacts.
- Use
LT_USERNAMEandLT_ACCESS_KEYfrom local environment variables or CI secrets; never hardcode credentials in YAML or docs. - Use
--job-secret-fileonly for extra job-scoped secrets, preferably outside the repo or ignored by.gitignore/.hyperexecuteignore. - Prefer template-driven YAML over generator scripts because test commands, paths, and payload boundaries are project-specific.
- Run safe local checks automatically; run real HyperExecute cloud jobs only after confirmation unless the user opted into autonomous mode.
- In autonomous mode, validate first, run, inspect output, download logs/artifacts when useful, and retry only for actionable config/environment fixes.
Workflow
- First run: analyze project, author YAML, run helper checks, run CLI validate, then request confirmation for the cloud job.
- Debug: reproduce the failing CLI command, add
--verbosewhen useful, download logs/artifacts/reports, fix one cause at a time. - CI: use CI secrets, add a validation stage before execution, set
CI=truefor quieter logs, and keep downloaded artifacts available for failed jobs. - Performance: tune
autosplit,concurrency, cache keys, retries, smart ordering, and matrix/hybrid scope after one successful run.
What ships with it
10 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.
- reference/ci-cd.md 1.9 KB
- reference/cli.md 2.8 KB
- reference/frameworks.md 2.7 KB
- reference/security.md 1.3 KB
- reference/troubleshooting.md 1.9 KB
- reference/yaml-patterns.md 1.6 KB
- scripts/build-command.js 2.0 KB runs code
- scripts/doctor.js 2.8 KB runs code
- scripts/summarize-artifacts.js 1.7 KB runs code
- scripts/validate-config.js 2.6 KB runs code
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.
- 10d ago First seen · 63 lines · 97 tokens per session scan A a5b1c3b82ec1
hyperexecute-skill is a skill published in the GitHub repository LambdaTest/agent-skills (366 stars, last pushed 1mo ago), licensed MIT. It adds 97 tokens to every session and 810 once invoked, about $0.0005 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-30.
Other skills, from other repositories
BrowserStack Cloud Testing
Cloud-based cross-browser and cross-device testing with BrowserStack including Automate, App Automate, Percy visual testing, Observability, and integration with Playwright, Selenium, and CI/CD pipelines.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).