Skip to content
Diagnosis · Automation

run-load-test

Run the Omnigent load test and produce a results file explaining the latencies.

Connecting the steps of a workflow

Works with
ClaudeChatGPTGeminiClaude CodeCodexCursorCopilotGemini CLI
Setup
Upload one file
About a minute in Claude. One command in coding tools.
Contains
Instructions only
Text files — no scripts or programs.
Maintained
Last change 5 Oct 2026
On the repository’s main branch.

What it does

Drives dev/loadtest/ end to end: collect inputs → run → read summary.md → explain the latencies. Each Locust user is a real `omnigent host` that registers over the host tunnel, creates host-bound sessions, and drives real multi-turn conversations — every turn is a genuine post→idle loop through the host's runner, with the LLM mocked (zero latency) so the numbers are Omnigent's own overhead.

Read more

-u N scales the number of hosts.

What it can touch

  • No script files in its folder

    Its folder holds text, not programs — but the instructions do tell your AI to run commands (see below).

    How we know

    Listed the one file in the skill’s folder on GitHub; none is a script or program.

  • Uses terminal commands

    It shows your AI commands to run. In a coding agent that means your terminal; in a chat app it usually can’t.

    How we know

    The SKILL.md contains shell code blocks.

  • No known risk pattern found

    Launch7’s automated check read all 1 text files in this skill and matched none of its risk patterns. This is not a guarantee: a check like this can miss new or disguised tricks, and the author can change the files after the check.

    How we know

    Read 2026-10-05, commit 4edb75c by pipeline/trust/analyze.py — 40+ patterns for hidden text, prompt injection, downloads that run, credential access and more. It reads; it never runs the skill.

  • Recently maintained

    Its repository has had changes recently.

    How we know

    Last push to omnigent-ai/omnigent: 2026-10-05 (0 days before the scan).

Read automatically from the skill’s own files on GitHub on 5 Oct 2026. Launch7 does not run or manually review skills: this lists what the check saw, and nothing here means “safe”. How we check

Add it to your AI

Supported. Upload it once in Claude’s settings. Works on every plan, including Free.

  1. Built in your browser from the SKILL.md on GitHub — nothing passes through Launch7.

  2. In Claude, open Customize → Skills, press +, then Create skill → Upload a skill, and choose the .zip.

  3. Make sure code execution is switched on (Settings → Capabilities). Skills need it.

  4. Start a new chat and ask for the job in your own words — Claude picks the skill up when it fits.

How Claude does this: support.claude.com · checked 28 Sep 2026 · “Supported” means documented by the vendor; Launch7 has not run it end to end

More from omnigent-ai

All from this publisher →
  • api-docs

    Document a module or public API surface (functions, classes, CLI commands, endpoints) from the code itself.

    omnigent-aiInstructions only
  • cross-review

    Verify an implementer's diff with an INDEPENDENT, different-vendor sub-agent (diff plus contract only); turn blocking issues into fix-tasks…

    omnigent-aiInstructions only
  • debate

    Have the Claude and GPT partners critique each other's answers across a configurable number of rounds (default 1) before converging on a synthesis.

    omnigent-aiInstructions only
  • deploy-docker-compose

    Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any…

    omnigent-aiReview before installing
  • detect-framework

    Detect Python agent frameworks from code imports and map them to Omnigent executor types.

    omnigent-aiInstructions only