ZeroG-KIT

A Windows CLI toolkit built in Python with 20 tools across 5 categories. Built during Hack Club Stardance as part of the Frictionless mission — the goal was to replace the habit of opening 5 different websites or apps for basic tasks and have everything in one terminal instead.

Requires admin rights on launch (auto-elevates via ctypes).

How to run

git clone https://github.com/otzpt/zeroG-KIT
cd zeroG-KIT
pip install -r requirements.txt
python main.py

Tools

System

• Clean Temp & Prefetch files
• View Clipboard
• System Info (OS, RAM, CPU, disk)
• Process Killer — lists top 30 by memory, kill by name

Utilities

• Image Converter (png, jpg, bmp, webp via Pillow)
• QR Code Generator
• Unit Converter (temperature, weight, length, data size)
• Password Generator
• Date & Time

Security

• Password Strength Checker
• SHA-256 Hashing
• Encrypt / Decrypt (AES via Fernet)
• Python Vulnerability Scanner (flags eval, exec, os.system, subprocess, pickle.loads)
• Firewall Check (profile state + RDP port 3389 exposure)

Network

• Ping host
• Local / Public IP lookup
• Port checker
• LAN active IP scanner

Text & Data

• Base64 encoder/decoder
• JSON Formatter (pretty-print with error handling)
• Case Converter (UPPER, lower, Title, camelCase, snake_case)
• Regex Tester
• Lorem Ipsum Generator

Tech stack

• Python 3
• psutil — process and system info
• Pillow — image conversion
• cryptography — AES encryption via Fernet
• qrcode — QR code generation
• Windows-only (netsh, ctypes, cls)

Structure

main.py         entry point, category submenus
utilities.py    system, image, QR, passwords, unit converter, process tools
security.py     hashing, password check, encryption, vuln scanner, firewall
network.py      ping, IP lookup, port checker, LAN scanner
text_tools.py   base64, JSON, case converter, regex, lorem ipsum

Challenges

The main challenge was scope. 20 tools is a lot to keep consistent — menu design, error handling, and UX all had to stay uniform across 5 different files. Early on everything was in a single utilities.py file; mid-project I refactored into modules by category which made it much easier to navigate and extend.

Error handling was another constant — every tool that touches files, network, or system calls needs try/except or it crashes on bad input. Adding that consistently across the whole toolkit took more time than the actual logic.

What I learned

• How to structure a medium-sized Python project with multiple modules
• try/except patterns for file, network, and system errors
• psutil for process and memory inspection
• AES encryption with cryptography.fernet
• How to use ctypes for Windows admin self-elevation