Echo RunPod
# Echo RunPod
Governed RunPod control plane for ECHO OMEGA PRIME. Version **1.1.1**.
One canonical policy source. Thin entry points for Grok, Codex, Echo agents, and ChatGPT-via-Nexus.
## Default
Observe and prepare. Do not spend unless the Commander approved a manifest or a bounded full lane is in force. Echo Nexus mutations require `confirm: EXECUTE`.
## ChatGPT / MCP
Dedicated resource (do **not** request `echo.write`):
- https://mcp.echo-op.com/oauth-mcp-runpod-v1
- live scopes: `echo.search` `echo.fetch` `echo.invoke.read` `echo.sdk.invoke`
- never: `echo.write`, `echo.read`, `echo.runpod.*`
- secret: `vault://runpod/api-key` then `RUNPOD_API_KEY`
`echo.sdk.invoke` keeps mutation tools mutating (`readOnlyHint: false`). They still require `confirm: EXECUTE` plus an approved manifest or bounded full lane.
## Install
See `skills/echo-runpod/references/install-verify.md`.
## Test
```bash
PYTHONPATH=. python -m unittest discover -s tests -v
```
## Upstream
- runpod/runpod-plugins-official v1.1.2 `b669407688056642d09d2049df5432cb78ae33f0`
- runpod/runpod-mcp `51d6fd9a0ff16a4eeb7d508972aeb5502f514939`
## Secrets
`vault://runpod/api-key` then `RUNPOD_API_KEY`. Never commit keys.
TDQS
Scored across 4 tools
search (query-based discovery) vs read (fetch an exact path/ID) vs write vs invoke_sdk_cap are largely distinct actions, and descriptions clarify the file-vs-SDK-capability duality. However, search and read both span files and SDK capabilities, creating mild overlap an agent could occasionally confuse when deciding whether to look up or fetch a record.
Three tools use terse single verbs (search, read, write) while one uses a fuller verb_noun form (invoke_sdk_cap); all are lowercase snake_case and verb-first. The pattern is readable and mostly consistent, with the one longer name being the only deviation.
Four tools is compact but each earns its place: discovery, read, write, and remote capability invocation cover the core surface of a file+SDK server. It is on the thin side but defensible for the focused scope.
The set exposes read, write/append (idempotent overwrite), search, and SDK invocation, but no delete or directory/list mutation is offered despite the file-oriented surface. Missing delete and any explicit listing/management operation is a notable gap agents will hit when housekeeping files.