BusyBox is a single binary that implements many common Unix tools.
Use this skill only on Windows. If you are on UNIX, then stop here.
Run the following steps only if you cannot find a busybox.exe file in the same directory as this document is.
These are PowerShell commands, if you have a classic cmd.exe terminal, then you must use powershell -Command "..." to run them.
- Print the type of CPU:
Get-CimInstance -ClassName Win32_Processor | Select-Object Name, NumberOfCores, MaxClockSpeed - Print the OS versions:
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object ProductName, DisplayVersion, CurrentBuild - Download a suitable build of BusyBox by running one of these PowerShell commands:
- 32-bit x86 (ANSI):
$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox.exe -OutFile busybox.exe - 64-bit x86 (ANSI):
$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox64.exe -OutFile busybox.exe - 64-bit x86 (Unicode):
$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox64u.exe -OutFile busybox.exe - 64-bit ARM (Unicode):
$ProgressPreference = 'SilentlyContinue'; Invoke-WebRequest -Uri https://frippery.org/files/busybox/busybox64a.exe -OutFile busybox.exe
- 32-bit x86 (ANSI):
Useful commands:
- Help:
busybox.exe --list - Available UNIX commands:
busybox.exe --list
Usage: Prefix the UNIX command with busybox.exe, for example: busybox.exe ls -1
If you need to run a UNIX command under another CWD, then use the absolute path to busybox.exe.
Documentation: https://frippery.org/busybox/ Original BusyBox: https://busybox.net/
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
AGI Framework Integration
Adapted for @techwavedev/agi-agent-kit Original source: antigravity-awesome-skills
Memory-First Protocol
Retrieve prior deployment configurations, rollback procedures, and incident post-mortems. Avoid re-discovering infrastructure patterns.
# Check for prior infrastructure context before starting
python3 execution/memory_manager.py auto --query "deployment configuration and patterns for Busybox On Windows"
Storing Results
After completing work, store infrastructure decisions for future sessions:
python3 execution/memory_manager.py store \
--content "Deployment pipeline: configured blue-green deployment with health checks on port 8080" \
--type technical --project <project> \
--tags busybox-on-windows devops
Multi-Agent Collaboration
Broadcast deployment changes so frontend and backend agents update their configurations accordingly.
python3 execution/cross_agent_context.py store \
--agent "<your-agent>" \
--action "Deployed infrastructure changes — updated CI/CD pipeline with new health check endpoints" \
--project <project>
Playbook Integration
Use the ship-saas-mvp or full-stack-deploy playbook to sequence this skill with testing, documentation, and deployment verification.