tool_profile · jdarmy, stowaway — Claude Code rule: Stowaway profile for agents
tool_profile — a Claude rule that profiles Stowaway: what the Go multi-hop proxy is built from, how it compiles, and which traces it leaves on a host.
MIT ★ 336 updated 2026-04-09
.claude/rules/tool_profile.mdWhat tool_profile does
The rule tool_profile.md hands a Claude agent a written profile of Stowaway, a Go multi-hop proxy that chains traffic through several nodes into an internal network. It separates the tool into admin, the operator console, and agent, the node planted on a target host, then goes through what the pair can do: multi-level SOCKS5, a remote shell, port forwarding, SSH tunnels, node reconnection.
What a defender gets is the detection block: process names stowaway_admin and stowaway_agent, flags such as --socks5-proxy and --tls-enable, protocol markers like IAMADMINXD and IAMNEWHERE, plus the startup log lines. Traffic runs under AES-256-GCM or TLS, so a review leans on those names and strings. Compiling from source uses the project Makefile with -trimpath -ldflags "-w -s", and Go 1.13+ is required.
What it helps with
- map the admin and agent halves of Stowaway before you touch a host
- spot the binary names and log lines that give a running agent away
- build per-platform binaries with the project Makefile
- explain which CLI flags a multi-hop proxy leaves in the process list
Example prompts for the agent
- Using the tool_profile notes, tell me which protocol strings leak Stowaway on the wire.
- Build Stowaway for Linux and macOS with the flags from the profile.
- What separates the admin console from an agent node?
How to install tool_profile
Manually: put the files in place
.claude/rules/tool_profile.mdThe paths frontmatter field limits the files
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.cursor/rules/tool_profile.mdcFrontmatter: description, globs, alwaysApply
Manually: put the files in place
.github/instructions/tool_profile.instructions.mdThe applyTo field sets which files it applies to
Manually: put the files in place
.devin/rules/tool_profile.mdManually: put the files in place
.clinerules/tool_profile.mdStep by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use
Questions about tool_profile
How do I install tool_profile in Claude Code?
Copy the rule file into your project at .claude/rules/tool_profile.md, and Claude picks it up as a project rule.
What does tool_profile do?
It describes Stowaway to the agent: the admin and agent components, their feature set, network markers and build steps. The agent answers questions about the tool from that description.
What is needed to build Stowaway?
Go 1.13+ and the project Makefile. The build runs with -trimpath -ldflags "-w -s" and writes binaries into release/.
Source text
tool_profile.md · MIT
# Tool Profile: Stowaway ## Basic Information | Attribute | Value | |-----------|-------| | Name | Stowaway | | Original Name | Stowaway | | Language | Go (Golang) | | Version | go 1.13+ | | Type | Multi-hop Proxy / Pivoting Tool | | Open Source | Yes | | Source URL | https://github.com/ph4ntonn/Stowaway | | Author | ph4ntonn | | License | MIT | ## Description Stowaway is a multi-hop proxy tool written in Go, designed for penetration testers. It allows users to proxy external traffic through multiple nodes into internal networks, bypassing network access restrictions and constructing a tree-like node network. ## Components | Component | File | Description | |-----------|------|-------------| | Admin | `admin/admin.go`, `admin/admin_win.go` | Controller interface used by penetration testers | | Agent | `agent/agent.go` | Controlled node deployed on target systems | ## Features - Multi-level SOCKS5 proxy (TCP/UDP, IPv4/IPv6) - Remote shell access - File upload/download - Port forwarding (local/remote) - SSH tunneling - Port reuse (SO_REUSEPORT, SO_REUSEADDR, iptables) - Node reconnection - Traffic encryption (AES-256-GCM, TLS) - Multiple protocol support (TCP, HTTP, WebSocket) - Cross-platform (Linux, Windows, macOS, MIPS, ARM, FreeBSD) ## Network Behavior | Feature | Details | |---------|---------| | Default Ports | User-defined via `-l` or `-c` | | Protocols | TCP, HTTP, WebSocket | | Encryption | AES-256-GCM, TLS | | Proxy Support | SOCKS5, HTTP proxy | ## Process Behavior | Feature | Details | |---------|---------| | Process Names | `stowaway_admin`, `stowaway_agent` | | CLI Arguments | `-l`, `-c`, `-s`, `--socks5-proxy`, `--http-proxy`, `--reconnect`, `--up`, `--down`, `--tls-enable` | ## File Behavior | Feature | Details | |---------|---------| | Output Files | None (in-memory operations) | | Config Files | None (CLI-based configuration) | ## String Constants ### Protocol Identifiers - `IAMADMINXD` - Admin UUID identifier - `IAMNEWHERE` - Temporary UUID for new connections - `THEREISNOROUTE` - Temporary route identifier ### Log Messages - `[*] Starting admin node on port` - `[*] Starting agent node` - `[*] Waiting for new connection` - `[*] Trying to connect node actively` ## Build System - Build tool: Go (Makefile) - Build flags: `-trimpath -ldflags "-w -s"` - Output: Multiple platform binaries in `release/` directory ## Detection Vectors 1. **Binary Names**: `stowaway_admin`, `stowaway_agent` 2. **CLI Arguments**: `-s`, `--socks5-proxy`, `--http-proxy`, `--reconnect`, `--tls-enable` 3. **Protocol Strings**: UUID identifiers in network traffic 4. **Log Messages**: Startup and connection messages 5. **Import Paths**: `Stowaway/` module path in Go binaries
© JDArmy · MIT · JDArmy/Evasion-SubAgents
Similar IDE rules
All IDE rules for Security →tool_profile by other authors comes first.