Big News: Socket raises $60M Series C at a $1B valuation to secure software supply chains for AI-driven development.Announcement
Sign In

@wipcomputer/wip-ai-devops-toolbox

Package Overview
Dependencies
Maintainers
1
Versions
83
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@wipcomputer/wip-ai-devops-toolbox

The complete AI DevOps toolkit for AI-assisted development teams.

latest
Source
npmnpm
Version
1.9.72
Version published
Maintainers
1
Created
Source
WIP Computer

npm CLI / TUI MCP Server OpenClaw Plugin Claude Code Skill Claude Code Hook Universal Interface Spec

AI DevOps Toolbox

Want your AI to dev? Here's what's working for us at WIP Computer.

Your AI writes code. But does it know how to release it? Check license compliance? Protect your identity files? Sync private repos to public? Follow a real development process?

AI DevOps Toolbox is the complete toolkit. Built by a team of humans and AIs shipping real software together.

Teach your AI to use DevOps Toolbox

Open your AI and paste this:

Read wip.computer/install/wip-ai-devops-toolbox.txt

Then explain:
1. What is AI DevOps Toolbox?
2. What does it install on my system?
3. What changes for us? (this AI)
4. What changes across all my AIs?

Check if AI DevOps Toolbox is already installed.

If it is, show me what I have and what's new.

Then ask:
- Do you have questions?
- Want to see a dry run?

If I say yes, run: ldm install wipcomputer/wip-ai-devops-toolbox --dry-run

Show me exactly what will change. Don't install anything until I say "install".

Your agent will read the spec, explain everything, and do a dry-run install first so you can see exactly what changes before anything is written to your system.

AI DevOps Toolbox Features

Every tool ships as one or more interfaces: the ways you and your AI can use it. CLI runs in your terminal. Module imports into your code. MCP connects to any AI that supports Model Context Protocol. OC Plugin plugs into the OpenClaw agent platform. Skill teaches your AI how to use the tool via a SKILL.md file (works in both Claude Code and OpenClaw). CC Hook runs automatically inside Claude Code on specific events.

As Andrej Karpathy said: "Apps are for people. Tools are for LLMs, and increasingly, LLMs are the ones using software."

Setup & Onboarding

Universal Installer

  • Teaches your AI to take anything you build and make it work across every AI interface. You write code in any language. This tool turns it into a CLI, MCP Server, OpenClaw Plugin, Skill, and Claude Code Hook. One command, all six interfaces.
  • Detects what a repo supports and deploys it all. Toolbox mode walks every sub-tool automatically
  • Interfaces: CLI, Module, Skill
  • Stable
  • Read more about Universal Installer

Dev Guide

  • Your team's conventions, baked in. Release process, repo structure, branch protection, the ai/ folder standard.
  • Best practices for AI-assisted development teams. Covers everything from branching to compliance
  • Read the Dev Guide

Infrastructure

LDM Dev Tools.app

  • Scheduled automation that runs whether anyone remembers or not. Backup, branch protection audit, visibility audit.
  • macOS .app bundle with Full Disk Access. One app to grant permissions to, one place to add new automation. Scripts can be run standalone without the .app
  • Stable
  • Read more about LDM Dev Tools.app

Repo Management

Repo Visibility Guard

  • Never accidentally expose a private repo.
  • Blocks repos from going public without a -private counterpart. Catches accidental exposure of internal plans, todos, and development context before it happens
  • Interfaces: CLI, Module, MCP, OpenClaw, Skill, CC Hook
  • Stable
  • Read more about Repo Visibility Guard

Repo Manifest Reconciler

  • Know where every repo belongs. One source of truth for folder structure.
  • Like prettier for folder structure. Move folders around all day; on sync, everything snaps back to where the manifest says
  • Interfaces: CLI, Module, MCP, Skill
  • Stable
  • Read more about Repo Manifest

Repo Init

  • Scaffold the standard ai/ directory in any repo. Plans, notes, ideas, dev updates, todos. One command.
  • New repo: creates the full structure. Existing repo: moves old ai/ contents to ai/_sort/ai_old/ so you can sort at your own pace. Nothing is deleted.
  • Interfaces: CLI, Skill
  • Stable
  • Read more about Repo Init

README Formatter

  • Generate or validate READMEs that follow the WIP Computer standard. Badges, title, tagline, "Teach Your AI" block, features, interface coverage table, license.
  • Generates separate section files (README-init-badges.md, README-init-features.md, etc.) so you can edit any section independently. Deploy assembles them into the final README. Same pattern as release notes: staging, review, deploy.
  • Interfaces: CLI, Skill
  • Stable
  • Read more about README Formatter

Forced Git Worktrees

  • Every repo uses git worktrees. Agents never edit on main. Period.
  • When an agent needs to make changes, it creates a worktree (isolated copy of the repo on its own branch). All edits happen there. Main stays clean. Multiple agents can work on the same repo simultaneously without collisions. When the work is done, it goes through a PR to merge back.
  • Interfaces: CLI, CC Hook
  • Stable

Branch Guard

  • Blocks all writes on main. The enforcement layer for forced worktrees.
  • PreToolUse hook that catches Write, Edit, and destructive Bash commands. Resolves the repo from the file path, not the CWD, so it works when Claude Code opens in a different directory. Read-only operations and merge/pull are still allowed on main.
  • Interfaces: CC Hook
  • Stable
  • Read more about Branch Guard

License, Compliance, and Protection

Identity File Protection

  • Know what it can never overwrite. CLAUDE.md, SOUL.md, MEMORY.md, SHARED-CONTEXT.md are permanently protected.
  • Blocks destructive edits to protected identity files. Your AI can read them but can't blow them away
  • Interfaces: CLI, Module, OpenClaw, Skill, CC Hook
  • Stable
  • Read more about Identity File Protection

License Guard

  • Enforce licensing on every commit. Copyright, dual-license, CLA. Checked automatically.
  • Ensures your own repos have correct copyright, license type, and LICENSE files. Interactive first-run setup. Toolbox-aware: checks every sub-tool. Auto-fix mode repairs issues
  • readme-license scans all your repos and applies a standard license block to every README in one command. Removes duplicate license sections from sub-tool READMEs
  • Interfaces: CLI
  • Stable
  • Read more about License Guard

License Rug-Pull Detection

  • Catch license changes in dependencies before they ship.
  • Scans every dependency for license changes. Blocks merges if a license changed upstream. Daily cron scan. Generates a public compliance dashboard
  • Interfaces: CLI, Module, MCP, Skill
  • Stable
  • Read more about License Detection

Release & Deploy

Release Pipeline

  • Release software correctly. Version bump, changelog, npm publish, GitHub release. One command, nothing forgotten.
  • SKILL.md sync, release notes on the branch for PR review. Warns when notes are too short or look like changelogs instead of narrative
  • Interfaces: CLI, Module, MCP, Skill
  • Stable
  • Read more about Release Pipeline

Private-to-Public Sync

  • Publish safely. Syncs private to public, excludes internal files, every time.
  • One script syncs your private working repo to a clean public mirror. Excludes internal ai/ folders automatically. Creates a PR, merges it, cleans up branches
  • Interfaces: CLI, Skill
  • Stable
  • Read more about Private-to-Public Sync

Post-Merge Branch Naming

  • Cleans up after itself. Merged branches get renamed with dates automatically.
  • Renames merged branches with --merged-YYYY-MM-DD. Preserves history without cluttering your branch list
  • Interfaces: CLI, Skill
  • Stable
  • Read more about Post-Merge Naming

Skill Publish to Website

  • After every release, your SKILL.md goes live as plain text on your website. No manual copying. No forgetting.
  • Add .publish-skill.json to your repo with name and websiteRepo. On release, SKILL.md is copied to yoursite.com/install/{name}.txt and deployed automatically. Any AI can fetch the URL and get clean, parseable instructions. Like robots.txt but for agent install prompts.
  • Interfaces: Module (built into Release Pipeline)
  • Stable

Make Discoverable in Claude Code

  • Turn any repo into a Claude Code plugin. Auto-generates .claude-plugin/plugin.json from your existing interfaces.
  • Runs during release. Detects what your repo exposes (skills, hooks, MCP servers, agents) and builds the plugin manifest so it shows up in Claude Code's /plugin marketplace. No manual config.
  • Interfaces: Module (built into Release Pipeline)
  • Planned

Interface Coverage

#ToolCLIModuleMCPOC PluginSkillCC Hook
Setup & Onboarding
1Universal InstallerYYY
2Dev Guide
Infrastructure
3LDM Dev Tools.app
Repo Management
4Repo Visibility GuardYYYYYY
5Repo Manifest ReconcilerYYYY
6Repo InitYY
7README FormatterYY
8Forced Git WorktreesYY
9Branch GuardY
License, Compliance, and Protection
10Identity File ProtectionYYYYY
11License GuardY
12License Rug-Pull DetectionYYYY
Release & Deploy
13Release PipelineYYYY
14Private-to-Public SyncYY
15Post-Merge Branch NamingYY
16Skill Publish to WebsiteY
17Make Discoverable in Claude CodeY

More Info

Part of LDM OS

AI DevOps Toolbox installs into LDM OS, the local runtime for AI agents. Run ldm install to see other components you can add.

License

Dual-license model designed to keep tools free while preventing commercial resellers.

MIT      All CLI tools, MCP servers, skills, and hooks (use anywhere, no restrictions).
AGPLv3   Commercial redistribution, marketplace listings, or bundling into paid services.

AGPLv3 for personal use is free. Commercial licenses available.

Can I use this?

Yes, freely:

  • Use any tool locally or on your own servers
  • Modify the code for your own projects
  • Include in your internal CI/CD pipelines
  • Fork it and send us feedback via PRs (we'd love that)

Need a commercial license:

  • Bundle into a product you sell
  • List on a marketplace (VS Code, JetBrains, etc.)
  • Offer as part of a hosted/SaaS platform
  • Redistribute commercially

Using these tools to build your own software is fine. Reselling the tools themselves is what requires a commercial license.

By submitting a PR, you agree to the Contributor License Agreement.

Built by Parker Todd Brooks, Lēsa (OpenClaw, Claude Opus 4.6), Claude Code (Claude Opus 4.6).

FAQs

Package last updated on 21 Apr 2026

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts