What is env-provisioning?

A procedure for starting a reproducible development environment and its supporting services so an application can be tested or run on its own.

Use it to detect the project's setup method, start services, verify that they work, and record the environment used for QA.

It reduces setup mistakes and makes repeated starts, health checks, and cleanup predictable.

env-provisioning — Skill for Claude Code by HigorAlves

Install

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.

Any agent

npx skills add HigorAlves/orc --skill env-provisioning

Clone the repo

git clone --depth 1 https://github.com/HigorAlves/orc

Made for: Claude Code.

Or install orc, the plugin that ships this one along with the rest of its 80 skills, 30 commands, 14 agents, 5 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/higoralves/orc/env-provisioning/github.svg)](https://agentmods.dev/skills/higoralves/orc/env-provisioning)

Your own site

<a href="https://agentmods.dev/skills/higoralves/orc/env-provisioning"><img src="https://agentmods.dev/badge/skills/higoralves/orc/env-provisioning/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/higoralves/orc/env-provisioning"><img src="https://agentmods.dev/badge/skills/higoralves/orc/env-provisioning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 68 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,527 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00068	$0.02527
Opus 5	$0.00034	$0.01264
Sonnet 5	$0.00014	$0.00505
Haiku 4.5	$0.00007	$0.00253

Measured 5d ago against content hash 0261ea7ae930, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

env-provisioning 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.

7. **Probe readiness** beyond compose health: `curl -sf <appUrl>` (retry ≤ 30s) and each HTTP endpoint in `serviceEndpoints`. Log every probe.

orc/skills/env-provisioning/SKILL.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Environment Provisioning

Stand up the app (and its backing services) so QA — or the user — can run against a real, reproducible environment. Honors the project's own setup guidelines when they exist; generates the minimum when they don't. Speed is a design goal: the second boot on a branch should take seconds, not minutes.

Announce at start: "I'm using the env-provisioning skill because this task needs the app running."

Deep Docker knowledge (multi-stage builds, hardening, compose patterns) lives in orc:docker-best-practices — reference it, never duplicate it. This skill owns the protocol: detect → provision → prove → record.

Detection ladder

Evaluate top-down in the worktree (the code under test), first hit wins. Setup guidelines (README/CONTRIBUTING "Setup"/"Getting started" sections, Makefile, .env.example) are consulted at EVERY rung — they supply env values, seed/migrate steps, ports, and the service list; they never override a higher rung's boot mechanism. Details + inference tables: references/detection.md.

Existing compose — compose.yaml|compose.yml|docker-compose.yml|docker-compose.yaml (+ overrides, dev profiles). This IS the project's runnable setup guideline. Use as-is; NEVER edit it — meet extra port/env needs with an orc-owned override file in .orc/<branch>/files/docker/.
Devcontainer — .devcontainer/devcontainer.json (or root variant). If it names dockerComposeFile → resolve to rung 1 with that file. Else wrap its image/Dockerfile in a generated compose honoring forwardPorts, containerEnv, postCreateCommand (as a one-shot).
Dockerfile — Dockerfile / Dockerfile.dev. Generate a compose: app builds from it (prefer a dev/development stage when multi-stage), plus inferred backing services.
Nothing — generate from analysis (references/generation.md). Default is hybrid: containers for backing services only (inferred from .env.example/config — DATABASE_URL→postgres, REDIS_URL→redis, …), app on the host via its dev script wired to them. Fastest and least invented; macOS bind-mount I/O makes containerized node dev servers slower. --containerize-app forces a full app container.

Read the full file on GitHub · 114 lines

Files

What ships with it

2 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.

Changes

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 · 114 lines · 68 tokens per session scan A 0261ea7ae930

Subscribe to this mod's changes

env-provisioning is a skill published in the GitHub repository HigorAlves/orc (6 stars, last pushed 12d ago), licensed MIT. It adds 68 tokens to every session and 2,527 once invoked, about $0.0003 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-09-03.

Containers DevOps and cloud Testing claude plugin

verify

Build the computer-use-demo image and drive the Streamlit UI headlessly to verify changes end-to-end.

anthropics/claude-quickstarts · 23 tokens

test-locally

Build and deploy a full local OpenMetadata stack with Docker to test your connector in the UI. Handles code generation, build optimization, health checks, and guided testing.

open-metadata/OpenMetadata · 38 tokens

redamon-testing

How RedAmon tests actually run and how to author them: the per-file Docker gate, the unit/integration/live tiers, and the failure modes that make a green run a lie. Trigger: editing any test.py, .test.ts(x) or tests/.sh; a test that is red, skipped or xfailed; a request to "run the tests", "make it green" or check…

samugit83/redamon · 114 tokens

env-provisioning