agentmods.dev

provision

A guided command for planning and creating cloud infrastructure with Terror, while asking for approval before changes are made.

In plain words
What is it for?
Use it to deploy sites, APIs, databases, storage, networking, or custom resources after choosing a provider and configuring regions, sizes, access, and dependencies.
Why use it?
It turns an infrastructure request into an explicit plan and shows what will be created, changed, or removed before execution.

Command for Claude Code

0 5mo ago A scan 10 tokens original MIT
View the source file lazorgurl/terror
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.

agentmods
npx agentmods add commands/lazorgurl/terror/provision
Clone the repo
git clone --depth 1 https://github.com/lazorgurl/terror

Made for: Claude Code.

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 406 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00010 $0.00406
Opus 5 $0.00005 $0.00203
Sonnet 5 $0.00002 $0.00081
Haiku 4.5 $0.00001 $0.00041

Measured yesterday against content hash 8fd0a29bbdb0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

provision scanned grade A with 0 findings 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 yesterday.

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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/plugins/terror/commands/provision.md · 46 lines

What it actually says

Provision Infrastructure

Walk the user through provisioning new cloud infrastructure with Terror.

Steps

  1. Gather requirements. Ask the user what they want to deploy:

    • Static site / CDN
    • API backend (Cloud Run, Lambda, ECS, etc.)
    • Database (Cloud SQL, RDS, PlanetScale, etc.)
    • Storage bucket
    • Networking (VPC, subnets, load balancer)
    • Custom / other

  2. Select provider. Ask which cloud provider (GCP, AWS, Azure) or confirm the default if one is configured. Call terror_status to see what providers are already in use.

  3. Configure. Based on the resource type, ask for:

    • Region / zone
    • Instance size or tier
    • Networking requirements (public/private, VPC)
    • Any dependencies on existing resources

  4. Build the plan. Use Terror's provider tools to construct the provisioning plan. For example:

    • gcp_compute_create for VMs
    • gcp_cloud_run_deploy for serverless containers
    • aws_rds_create for databases Present the plan to the user before executing.

  5. Decision gate. This is critical. Before executing any mutating operation:

    • Show exactly what will be created, modified, or destroyed
    • Show estimated cost impact if available
    • Ask for explicit confirmation
    • If the user says no, offer to modify the plan

  6. Execute. Run the plan and report results. Call terror_health on newly created resources to verify they came up correctly.

  7. Post-provision. Suggest next steps:

    • Run /inspect to verify the new resources
    • Run /doc-infra to update documentation
    • Set up monitoring or alerts if applicable
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.

  1. yesterday First seen · 46 lines · 10 tokens per session scan A 8fd0a29bbdb0

Subscribe to this mod's changes

provision is a command published in the GitHub repository lazorgurl/terror (0 stars, last pushed 5mo ago), licensed MIT. It adds 10 tokens to every session and 406 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

DevOps and cloudPlanning
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens

implement

Execute the implementation plan by processing and executing all tasks defined in tasks.md.

github/spec-kit · 14 tokens