infra-ops

Operate private infrastructure through redacted helpers, safety tiers, and guarded API mutations.

5|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cbusillo/codex-skills --skill infra-ops-cbusillo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: infra-ops
Source: https://github.com/cbusillo/codex-skills/tree/main/skills/infra-ops
Command: npx skills add https://github.com/cbusillo/codex-skills --skill infra-ops-cbusillo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pytest, and includes scripts (resource) and references (resource) components.

What problem does it solve? Operating private infrastructure from a public skill repository risks leaking hostnames, credentials, topology, and secrets into public outputs, while unguarded writes can cause production outages. This Skill enforces a strict public/private boundary: all environment-specific facts live in a private operations repo resolved through a local context pointer, and every operation is classified into safety tiers before execution. ## Core Features & Use Cases - Tiered safety workflow: Classifies work as read-only inventory, reversible pilot writes, or production-impacting mutations, requiring approval, identity checks, and rollback plans before any apply. - Redacted NPMplus operations engine: Ships a generic Python CLI for NPMplus proxy-host inventory, pilot status, and lifecycle enable/disable with per-ref authorization, identity fingerprint verification, and write-evidence gates. - Private context discovery: Resolves the private operations repo from $CODE_HOME, $CODEX_HOME, or ~/.code local-context.toml files without ever printing private paths or values. - Use Case: An operator needs to disable a canary proxy host in NPMplus. The Skill validates the private context schema, confirms the authenticated principal and target domain fingerprint, checks snapshot/rollback readiness booleans, runs a dry-run, and only then applies the mutation with redacted output. ## Quick Start Ask the agent to check whether private infra context is configured and show the redacted NPMplus pilot status before planning any change.

Frequently Asked Questions about infra-ops

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely run NPMplus proxy host changes from an AI agent?

Use the npmplus-ops.py engine with a private context provider. Run a lifecycle dry-run first to see apply_authorized and apply_ready booleans, then apply only when the v2 context allows the action and all write-evidence gates are true.

How does the skill find my private infrastructure repo?

It reads the [docs].local_infra pointer from local-context.toml, checking $CODE_HOME first, then $CODEX_HOME, then ~/.code. An explicit --local-context flag overrides discovery and never falls back.

Can the NPMplus engine leak private hostnames or credentials?

No. The engine outputs only counts, booleans, and public-safe ref aliases. Provider failures, HTTP errors, and env values are redacted, and tests assert private literals never appear in output or help text.

Why does an NPMplus lifecycle apply fail with schema version errors?

Lifecycle writes require the npmplus.ops.v2 context schema. Legacy v1 contexts remain read-only during migration, so --apply is rejected until the private provider emits v2 with per-ref allowed actions and write evidence.

What happens if private infra context is not configured?

The workflow stays read-only. The private-context-check script prints only configured or missing without disclosing paths, and the skill instructs the agent not to guess from dashboards, shell history, or .env files.