Jasper ConfigGuard

Safely apply OpenClaw config changes with backup, automatic rollback on failure, health checks, and commands for patching, restoring, listing, diffing, valid...

Security Scan

The skill is internally consistent with its stated purpose (safe OpenClaw config changes with backups and rollback); it modifies local OpenClaw config, creates backups, and may restart the gateway — behavior matches the documentation and code.

Purpose & Capability

Name/README/SKILL.md all describe safe edits to an OpenClaw config and rollback behavior. The code operates on ~/.openclaw/openclaw.json (or cwd/openclaw.json), posts health-checks to localhost:18789, creates backups, writes files, and issues pgrep/kill commands to the gateway process — all coherent with a config-guard tool.

Instruction Scope

SKILL.md instructs installation via npm and shows CLI/programmatic usage that reads/writes ~/.openclaw/openclaw.json, manages backups in ~/.openclaw/config-backups/, and restarts the gateway. Those operations are expected for the tool, but the registry metadata did not declare any required config paths or filesystem access; the instructions explicitly require write access to ~/.openclaw which should be noted.

Install Mechanism

The skill bundle includes full source files but provides no install spec in the registry. SKILL.md instructs users to install via `npm install -g jasper-configguard` (which downloads code from the npm registry). No download-from-untrusted-URL or extraction steps are present in the manifest — risk is standard for installing an npm package; verify package provenance before global install.

Credentials

No environment variables or secrets are requested. The code uses HOME to locate config paths and expects write access to those paths. It does not request or transmit credentials or contact external endpoints beyond the local gateway (http://localhost:18789).

Persistence & Privilege

The skill will modify local configuration files and attempt to restart the gateway using OS signals (pgrep/kill). That is an expected privilege for a config management tool but is a privileged action on the host — consider whether the agent runtime should be allowed to perform these operations automatically.

Assessment

This package appears to do what it says: it reads/writes your OpenClaw config (~/.openclaw/openclaw.json), stores backups in ~/.openclaw/config-backups/, and may restart the gateway process (pgrep/kill). Before installing or letting an agent invoke it autonomously, consider: (1) Verify the package source (npm name, repository, owner) and that you trust the publisher. (2) Back up your current config manually. (3) Run it in a non-production environment first (use --dry-run and --no-restart). (4) Ensure the agent/runtime has only the minimum permissions you are comfortable with — this tool needs filesystem write access and the ability to signal processes. (5) Note the minor metadata mismatch: the registry metadata lists no required config paths, but the tool expects ~/.openclaw; ensure path expectations match your deployment. If you want stricter control, require manual confirmation for patches or avoid enabling autonomous invocation for this skill.

Jasper ConfigGuard v1.0.0

Safe config changes for OpenClaw with automatic rollback. Never brick your gateway again.

Setup

npm install -g jasper-configguard

Usage

Apply a config change safely

jasper-configguard patch '{"gateway":{"bind":"tailnet"}}'

The tool will:

1. Back up your current config
2. Apply the patch (deep merge)
3. Restart the gateway
4. Wait for health check
5. Auto-rollback if gateway fails

Preview changes

jasper-configguard patch --dry-run '{"agents":{"defaults":{"model":{"primary":"opus"}}}}'

Restore from backup

jasper-configguard restore

List backups

jasper-configguard list

Check health

jasper-configguard doctor

Agent Integration

Use from your agent to safely modify OpenClaw config:

# Safe model switch
jasper-configguard patch '{"agents":{"defaults":{"model":{"primary":"anthropic/claude-opus-4-5"}}}}'

# Enable a plugin safely
jasper-configguard patch '{"plugins":{"entries":{"my-plugin":{"enabled":true}}}}'

# If something breaks, restore
jasper-configguard restore

API

const { ConfigGuard } = require('jasper-configguard');
const guard = new ConfigGuard();

// Safe patch
const result = await guard.patch({ gateway: { bind: 'tailnet' } });
if (!result.success) console.log('Rolled back:', result.error);

// Dry run
const preview = guard.dryRun({ agents: { defaults: { model: { primary: 'opus' } } } });
console.log(preview.diff);