Infra Wrapper

v1.0.0

Terragrunt is a flexible orchestration tool that allows Infrastructure as Code written in OpenTofu/T terraform-wrapper, go, aws, cli, developer-tools.

0· 145·1 current·1 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for bytesagain1/infra-wrapper.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Infra Wrapper" (bytesagain1/infra-wrapper) from ClawHub.
Skill page: https://clawhub.ai/bytesagain1/infra-wrapper
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install infra-wrapper

ClawHub CLI

Package manager switcher

npx clawhub@latest install infra-wrapper
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description say it's a Terragrunt/Infra wrapper for recording and analyzing runs; the code implements a local logging utility that records timestamped entries, exports/searches them, and reports status. No access to unrelated services or credentials is requested.
Instruction Scope
SKILL.md and the script limit actions to local logging, searching, exporting, and status checks in ~/.local/share/infra-wrapper. Note: the tool records arbitrary user-provided command strings — if you log commands that include secrets or credentials, those will be stored in plaintext logs. Exports (json/csv/txt) will include those entries.
Install Mechanism
There is no install spec and no remote download; the skill is instruction-only and includes a local shell script. Nothing is fetched from external URLs or installed system-wide by the skill.
Credentials
The skill requests no environment variables, no credentials, and no config paths beyond writing to ~/.local/share/infra-wrapper. This is proportionate to a local logging utility.
Persistence & Privilege
The skill does not request always:true, does not modify other skills or system-wide settings, and only persists its own log files under the user's home directory.
Assessment
This skill is a local logger for infra commands and appears to do only file I/O under ~/.local/share/infra-wrapper. Before installing or using it: inspect the script yourself, and be careful not to pass secrets or long-lived credentials on the command line (they will be saved in plaintext logs and included in exports). Consider restricting the data directory permissions (chmod 700 ~/.local/share/infra-wrapper), deleting sensitive log entries, or running the tool in an isolated environment if you need caution. If you expect any network behavior or external integrations, verify the author/source — this package has no homepage and comes from an unknown source.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bfbrb525zq4bwt4j71t467d8399qh
145downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

Infra Wrapper

Infra Wrapper v2.0.0 — a utility toolkit for running, checking, converting, analyzing, generating, previewing, batching, comparing, exporting, configuring, monitoring status, and reporting on infrastructure wrapper operations. All entries are timestamped and logged locally for history tracking.

Commands

Core Commands

  • run <input> — Record and log a run entry. Without arguments, shows the 20 most recent run entries.
  • check <input> — Record and log a check entry. Without arguments, shows recent check entries.
  • convert <input> — Record and log a convert entry. Without arguments, shows recent convert entries.
  • analyze <input> — Record and log an analyze entry. Without arguments, shows recent analyze entries.
  • generate <input> — Record and log a generate entry. Without arguments, shows recent generate entries.
  • preview <input> — Record and log a preview entry. Without arguments, shows recent preview entries.
  • batch <input> — Record and log a batch entry. Without arguments, shows recent batch entries.
  • compare <input> — Record and log a compare entry. Without arguments, shows recent compare entries.
  • export <input> — Record and log an export entry. Without arguments, shows recent export entries.
  • config <input> — Record and log a config entry. Without arguments, shows recent config entries.
  • status <input> — Record and log a status entry. Without arguments, shows recent status entries.
  • report <input> — Record and log a report entry. Without arguments, shows recent report entries.

Utility Commands

  • stats — Show summary statistics across all log files (entry counts per type, total entries, disk usage).
  • export <fmt> — Export all logged data to a file. Supported formats: json, csv, txt. (Note: also doubles as a core command when given non-format arguments.)
  • search <term> — Search all log files for a case-insensitive term match.
  • recent — Show the 20 most recent entries from the activity history log.
  • status — Health check showing version, data directory, total entries, disk usage, and last activity. (Note: also doubles as a core command when given arguments.)
  • help — Display the full help message with all available commands.
  • version — Print the current version (v2.0.0).

Data Storage

All data is stored in ~/.local/share/infra-wrapper/:

  • Each core command writes timestamped entries to its own log file (e.g., run.log, check.log, batch.log).
  • A unified history.log tracks all operations across commands.
  • Export files are written to the same directory as export.json, export.csv, or export.txt.

Requirements

  • Bash (with set -euo pipefail)
  • Standard Unix utilities: date, wc, du, tail, grep, sed, cat, basename

When to Use

  • When you need to log and track infrastructure wrapper operations (runs, checks, conversions, batch jobs, etc.)
  • For maintaining an audit trail of Terragrunt/OpenTofu/Terraform orchestration activities
  • To analyze and compare infrastructure configurations with timestamped records
  • To export accumulated infra wrapper data in JSON, CSV, or plain text for downstream processing
  • As part of a larger IaC automation pipeline that needs timestamped operation records
  • When you need to search across historical infrastructure orchestration entries
  • For batch processing multiple infrastructure operations and tracking their status

Examples

# Run an operation
infra-wrapper run "terragrunt apply --all"

# Check configuration
infra-wrapper check "module dependencies in staging"

# Convert infrastructure format
infra-wrapper convert "HCL to JSON for ci pipeline"

# Analyze infrastructure
infra-wrapper analyze "cost impact of scaling change"

# Generate configurations
infra-wrapper generate "module boilerplate for new service"

# Preview changes before applying
infra-wrapper preview "plan output for production"

# Batch process operations
infra-wrapper batch "apply all modules in us-east-1"

# Compare environments
infra-wrapper compare "staging vs production configs"

# Update config
infra-wrapper config "set backend to s3://terraform-state"

# View recent activity
infra-wrapper recent

# Search across all logs
infra-wrapper search "production"

# Export everything to CSV
infra-wrapper export csv

# Show stats
infra-wrapper stats

# Health check
infra-wrapper status

Output

All commands output results to stdout. Redirect to a file if needed:

infra-wrapper stats > report.txt
infra-wrapper export json

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com

Comments

Loading comments...