agentiko-worker

Operate restricted Alpine Linux containers for reconnaissance and penetration testing tasks.

1.1k|191|Updated Jun 24, 2026
One-click install
npx skills add https://github.com/uphiago/recon-skills --skill agentiko-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentiko-worker
Source: https://github.com/uphiago/recon-skills/tree/main/agentiko-worker
Command: npx skills add https://github.com/uphiago/recon-skills --skill agentiko-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about agentiko-worker

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run long-running nmap scans in a remote SSH terminal without losing progress?

To run long-running nmap scans in a remote SSH terminal, use tmux to keep the process alive across disconnections. You can execute your full port scan and save the results directly to the persistent /root/output/ directory.

How do I bypass write_file restrictions when saving pentest recon output in Alpine Linux?

To bypass write_file restrictions in Alpine Linux, use terminal-based Python file writes to save your pentest recon output. This workaround allows you to persist results in the /root/output/ directory without hitting container path blocks.

Why does masscan fail on Alpine Linux and how do I fix it?

Masscan fails on Alpine Linux due to missing libpcap dependencies. The environment provides specific fixes for this issue, allowing you to successfully execute masscan alongside other pre-installed recon tools like nmap and ffuf.

Can I extract content from Vercel Next.js RSC targets that block automated requests?

Yes, you can extract content from Vercel Next.js RSC targets that block automated requests. The environment provides specific guidance for RSC content extraction to bypass restrictions during offensive security reconnaissance.

What pre-installed recon tools are available in a restricted remote worker container?

Pre-installed recon tools in the restricted remote worker container include nmap, nuclei, and ffuf. The environment offers a full inventory of these offensive security tools along with guidance for navigating container architecture boundaries.

How do I set up continuous reconnaissance using cron in an Alpine Linux worker?

To set up continuous reconnaissance in an Alpine Linux worker, use cron-based scheduling combined with tmux. This operational best practice ensures your automated pentest recon tasks persist and run seamlessly within the container environment.