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 agentmods add skills/orka-agents/orka/agent-substrate-deploynpx skills add orka-agents/orka --skill agent-substrate-deploygit clone --depth 1 https://github.com/orka-agents/orkaWrote 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/orka-agents/orka/agent-substrate-deploy)<a href="https://agentmods.dev/skills/orka-agents/orka/agent-substrate-deploy"><img src="https://agentmods.dev/badge/skills/orka-agents/orka/agent-substrate-deploy.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00086 | $0.03842 |
| Opus 5 | $0.00043 | $0.01921 |
| Sonnet 5 | $0.00017 | $0.00768 |
| Haiku 4.5 | $0.00009 | $0.00384 |
Grade A, and why
agent-substrate-deploy scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`jq`, `kubectl`, `curl` (and `gh` for the git-token convenience). Put the Go How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Substrate Deploy
Stand up Agent Substrate and an
Orka-compatible WorkerPool + ActorTemplate on a local kind cluster, wire Orka
with --substrate-* flags, then validate the direct Substrate actor/router and
MCP tool paths. type: agent Tasks whose spec.execution.workspace uses
provider: substrate are flag-gated: without
--acp-workspace-dispatch-enabled they fail closed. The bundled installer/E2E
enables the gate by default, uses the required infrastructure templateRef,
and runs a real Codex prompt against a local Responses-compatible fixture in a
Substrate Actor behind a dedicated acp-ws-* RuntimePool (ADR 0025).
This skill is for local/kind evaluation and validation, not production. Orka
does not install or manage Substrate (CRDs, control plane, router, snapshot
store, WorkerPool capacity) in production. See
website/docs/concepts/substrate.md for the full design, controller flags, and
ActorTemplate compatibility contract.
What this skill orchestrates (do not retype)
The repeatable standup already lives in
hack/demos/cluster/install-substrate.sh, a thin KEEP_CLUSTER=1 wrapper over
the CI-proven scripts/agent-substrate-e2e.sh. Drive the installer in place;
do not copy either script into the skill. They pin the Substrate revision
(SUBSTRATE_REF, default b80031d260959b1fc5c6f61e3099fe2a6d368af1) and own the
heavy lifting: clone Substrate at the pinned ref, create the kind cluster + local
registry, deploy the ate-system control plane, build/push the controller, workspace-agent, MCP server, and tool-client images;
publish the Substrate ateom-gvisor image; create a WorkerPool + gVisor
ActorTemplate, initialize the RustFS snapshot bucket, and deploy Orka
wired with --substrate-*. Re-pin by overriding SUBSTRATE_REF, not by editing
a copy. The installer also applies the reviewed
hack/agent-substrate/atelet-root-supervisor-capabilities.patch compatibility
patch before installation. It verifies the pinned upstream atelet OCI source
blob first, scopes the extra capabilities to the /orka-workspace-agent
entrypoint, and fails closed on changed context, so a SUBSTRATE_REF override
may require reviewing and updating or removing that patch.
What ships with it
3 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.
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.
- 5d ago First seen · 298 lines · 86 tokens per session scan A 63a2ba30722b
agent-substrate-deploy is a skill published in the GitHub repository orka-agents/orka (21 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 3,842 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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 container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.