terminal-env

Manage sandboxed terminal sessions with tmux and timestamped command logging.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/noname300989/Security-Claw --skill terminal-env
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: terminal-env
Source: https://github.com/noname300989/Security-Claw/tree/main/skills/terminal-env
Command: npx skills add https://github.com/noname300989/Security-Claw --skill terminal-env

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires tmux, bash, python3, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a robust and auditable way to manage interactive terminal sessions, crucial for executing commands, running tools, and collecting evidence during red team operations.

Core Features & Use Cases

  • Sandboxed Shell Execution: Safely run commands and tools within managed environments.
  • Persistent Sessions: Utilize tmux for maintaining sessions across different phases of an engagement.
  • Audit Trails: Automatically log all commands with timestamps for comprehensive evidence collection.
  • Parallel Execution: Run multiple tools concurrently to speed up reconnaissance and scanning.
  • Use Case: During a penetration test, you can use this skill to start a tmux session with separate windows for reconnaissance, web application testing, and active directory enumeration, ensuring all actions are logged for reporting.

Quick Start

Use the terminal-env skill to start a new tmux session named 'engagement' with windows for recon, web, and ad.

Frequently Asked Questions about terminal-env

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

FAQPage Schema
How do I manage persistent terminal sessions for red team operations?

You can manage persistent terminal sessions for red team operations by utilizing tmux to maintain interactive shell environments across different phases of an engagement, ensuring continuous execution and sandboxed command logging.

What is the best way to log shell commands with timestamps for auditing?

The best way to log shell commands with timestamps for auditing is to execute tools within a managed terminal environment that automatically records all command-line activity into comprehensive evidence trails.

Can I run parallel tools concurrently across bash and Python REPL?

Yes, you can run parallel tools concurrently across bash and Python REPL by using tmux to create separate windows for different tasks, speeding up reconnaissance and scanning during penetration tests.

Does terminal-env support sandboxed shell execution for penetration testing?

Yes, terminal-env supports sandboxed shell execution for penetration testing by safely running commands and tools within managed environments to isolate active directory enumeration and web application testing.

Do I need tmux and python3 to maintain shell environments for engagements?

Yes, you need tmux, bash, and python3 installed as dependencies to maintain persistent shell environments, manage parallel tool execution, and support Python REPL for red team engagements.

When should I use managed terminal environments instead of standard shells?

You should use managed terminal environments instead of standard shells when you need comprehensive audit trails, sandboxed execution, and persistent session management for collecting evidence during red team operations.