Execgo agent bridge

Skill iammm0/secbot/skills/custom/execgo-agent-bridge

Authorized security testing workspace. v2 TypeScript terminal product on release; v1 Python on pypi-release; Go branch is demo only.

Install

npx -y skills add iammm0/secbot --skill execgo-agent-bridge

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

What its author says it does

Copied from the file, not written here

Route shell, runtime.command, runtime.script, mcp.call, cli.run, or task_graph.submit work through Secbot's ExecGo-backed control tools.

SKILL.md

3.3 KB, 778 tokens by cl100k_base, as published. Nobody here has run it

Overview

Use this skill when work should run through ExecGo instead of ad-hoc local execution. In this repository, the primary bridge is the execgo_action tool, and execute_command can also route through ExecGo when execgo=true or SECBOT_EXECGO_ENABLED=1 is active.

When To Use

You need reliable task IDs, wait semantics, cancellation, timeout control, or runtime-backed execution.
You want to submit runtime.command, runtime.script, mcp.call, cli.run, or task_graph.submit actions.
You need a structured smoke test before attempting a side-effecting ExecGo action.

Rules

Prefer execgo_action over hand-written HTTP calls.
Use mode=health or mode=tools first if ExecGo availability is unknown.
Use a stable action_id when subsequent waits or logs need correlation.
Start with kind=os.noop for connectivity checks before side-effecting actions.
For plain shell execution, prefer execute_command; only force ExecGo when the job benefits from ExecGo task handling.

Tool Mapping In This Repo

execgo_action:
- mode=health checks ExecGo health.
- mode=tools lists adapter capabilities.
- default mode=act submits an action and waits by default.
execute_command:
- pass execgo=true to route command execution through ExecGo runtime.command.
- does not currently support cwd or stdin_data in ExecGo mode.

Recommended Flow

Call execgo_action with {"mode":"health"}.
Call execgo_action with {"mode":"tools"} if you need capability discovery.
Submit os.noop for a smoke test.
Submit the real action with a stable action_id and structured input.
If the action is a simple shell command and fits the local bridge, use execute_command with execgo=true instead of building the JSON manually.

Examples

Smoke test via execgo_action:

{
  "kind": "os.noop",
  "action_id": "smoke-noop-1",
  "input": {
    "message": "hello execgo"
  }
}

Runtime command via execgo_action:

{
  "kind": "runtime.command",
  "action_id": "runtime-echo-1",
  "input": {
    "program": "/bin/sh",
    "args": ["-c", "echo hello execgo-runtime"],
    "limits": {
      "wall_time_ms": 30000
    }
  }
}

Shell command via execute_command:

{
  "command": "uname -a",
  "timeout": 30,
  "execgo": true
}

Environment Notes

EXECGO_URL defaults to http://127.0.0.1:8080.
EXECGO_RUNTIME_URL defaults to http://127.0.0.1:18080.
EXECGO_EXECGOCLI can point to a non-default execgocli binary.
SECBOT_EXECGO_ENABLED=1 makes execute_command prefer ExecGo by default.

References

references/action-contract.md for the action envelope and kinds.
references/runtime-operations.md for runtime startup and readiness expectations.
references/agent-specific-notes.md for notes about fitting the upstream skill into Secbot.
references/troubleshooting.md for common failures.