agentiko-worker

What problem does it solve?

This Skill eliminates confusion and friction when operating in a restricted remote Alpine Linux worker container for offensive security reconnaissance and penetration testing, removing guesswork about environment boundaries, tool availability, path restrictions, and common Alpine-specific pitfalls.

Core Features & Use Cases

• Clear Architecture Guidance: Explicit breakdown of the two-container agentiko setup, so you always know which resources are accessible from the worker vs the Hermes host.
• Tool & Workaround Inventory: Full list of pre-installed recon tools (nmap, nuclei, ffuf, etc.) with fixes for common issues like missing libpcap for masscan, and workarounds for the Hermes write_file path restriction.
• Operational Best Practices: Guidance for long-running scans with tmux, cron-based continuous recon, and Vercel Next.js RSC content extraction for targets that block automated requests.
• Use Case: When running a full port scan of a target, use the documented tmux pattern to keep the scan alive across terminal disconnections, and save results to the persistent /root/output/ directory without hitting write_file blocks.

Quick Start

Use the agentiko-worker skill to run a full nmap scan of target.com, save the results to /root/output/nmap-results, and work around any write_file restrictions by using terminal-based Python file writes.