🎯 Modern pentest command launcher written in Go!

Inspired by arsenal, rewritten from scratch with a focus on simplicity, speed and developer experience.

go install -v github.com/halilkirazkaya/arsenal-ng/cmd/arsenal-ng@latest

Requires Go 1.24.0 Ensure $(go env GOPATH)/bin is in your $PATH.

git clone https://github.com/halilkirazkaya/arsenal-ng.git
cd arsenal-ng
make build
./bin/arsenal-ng

You can create an alias for quick access (e.g., a):

Zsh:

echo "alias a='arsenal-ng'" >> ~/.zshrc
source ~/.zshrc

Bash:

echo "alias a='arsenal-ng'" >> ~/.bashrc
source ~/.bashrc

# Launch the application
arsenal-ng

# The TUI will open with all available commands
# Use arrow keys to navigate, type to search, Enter to select

The selected command will appear in your terminal input buffer, ready to edit and execute.

1. Search for a command: Type keywords (e.g., nmap scan, ffuf)
2. Navigate results: Use arrow keys to browse matching commands
3. Select command: Press Enter on the desired command
4. Fill arguments: If the command has {{placeholders}}, fill them in
5. Execute: Press Enter to write the command to your terminal

# 1. Launch arsenal-ng
arsenal-ng

# 2. Set global variables (type in search box)
set target=10.10.10.10

# 3. Search for nmap commands
nmap

# 4. Select "nmap - syn stealth scan"
# The {{target}} placeholder is auto-filled with 10.10.10.10!

# 5. Command appears in terminal:
nmap -sS 10.10.10.10

# 6. Edit if needed, then press Enter to execute

Set variables once and reuse them across all commands in your session. Variables automatically pre-fill argument fields in commands.

1. Type set ip=10.10.10.10 and press Enter
2. Select any command with {{ip}} placeholder
3. The ip field will be pre-filled automatically with 10.10.10.10
4. You can still edit the pre-filled value if needed
5. Variables persist throughout your session until you exit or unset them

# Set common variables at the start of your session
set ip=10.10.10.10
set domain=corp.local
set user=administrator

# Now select any command - arguments will auto-fill!
# Before: nmap -sV {{ip}}
# After:  nmap -sV 10.10.10.10  (auto-filled!)

# View all variables
variables

# Remove a variable when done
unset ip

Add your own commands by creating YAML files in internal/loader/cheat-files/:

tool: mytool
tags: [recon, web, custom]

actions:
  - title: mytool - basic scan
    desc: Performs a basic scan against the target
    command: "mytool scan {{target}}"

  - title: mytool - scan with multiple arguments
    desc: Advanced scan with IP, port, and output file
    command: "mytool scan -t {{ip}} -p {{port|443}} -o {{output|scan.log}}"

• tool: Tool name (e.g., nmap, ffuf, gobuster)
• tags: Array of tags for categorization (e.g., [recon, scan, network])
• actions: List of command entries
  • title: Display name shown in the list
  • desc: Optional description (shown in info box)
  • command: Command template with {{placeholders}}

• Use descriptive titles that make it easy to find commands
• Add relevant tags for better searchability
• Use default values for commonly used options
• Global variables will auto-fill matching argument names

• Go 1.24.0 or higher
• Make (optional, for using Makefile)

git clone https://github.com/halilkirazkaya/arsenal-ng.git
cd arsenal-ng
make build
# Binary will be in ./bin/arsenal-ng

Or build directly with Go:

go build -o bin/arsenal-ng ./cmd/arsenal-ng

1. Create a new YAML file in internal/loader/cheat-files/
2. Follow the format above (see Cheat File Format)
3. Rebuild: make build

After making changes, rebuild and test:

make build
./bin/arsenal-ng

• Follow Go code style conventions
• Keep YAML files organized and well-documented
• Add descriptive titles and tags to commands
• Test your changes before submitting PRs

The TIOCSTI ioctl is disabled by default in newer Linux kernels for security reasons. Enable it:

# Temporary (current session only)
sudo sysctl -w dev.tty.legacy_tiocsti=1

# Permanent (survives reboot)
echo "dev.tty.legacy_tiocsti=1" | sudo tee /etc/sysctl.d/99-tiocsti.conf
sudo sysctl --system

This project is open source and contributions are welcome!

• 🔧 Add a tool: Create a YAML file in internal/loader/cheat-files/ and submit a PR
• 🐛 Report bugs: Open an issue with details about the problem
• 💡 Suggest features: Share your ideas for improvements
• 📝 Improve documentation: Help make the README and code comments better
• ⭐ Star the project: Show your support!

The easiest way to contribute is by adding new cheat sheet YAML files:

1. Fork the repository
2. Add your YAML file(s) to internal/loader/cheat-files/
3. Follow the existing format and style
4. Test your changes locally
5. Submit a pull request

See Cheat File Format for details.

Made with ❤️ and Bubble Tea