terminal-ops

Capture timestamped, tamper-evident terminal commands with status markers during pentests.

60|14|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/brucesongs/kali-claw --skill terminal-ops-brucesongs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: terminal-ops
Source: https://github.com/brucesongs/kali-claw/tree/main/skills/terminal-ops
Command: npx skills add https://github.com/brucesongs/kali-claw --skill terminal-ops-brucesongs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces an evidence-first execution workflow so every terminal command in a penetration test is captured with timestamps, outputs, and a verifiable execution state, enabling auditability, reproducibility, and defensible reporting.

Core Features & Use Cases

  • Evidence-chain protocol: Every action is wrapped with metadata, output, and status markers to create a traceable execution history.
  • Structured artifacts: Supports session recordings, hashes, and standardized evidence files to support post-engagement reporting.
  • Deterministic orchestration: Defines a disciplined five-phase workflow (resolve, read failing surface, execute, verify, report) to guide all terminal operations during engagements.

Quick Start

Start a new session with automated evidence capture, then run your first command and verify an evidence block is generated.

Frequently Asked Questions about terminal-ops

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

FAQPage Schema
How do I capture tamper-evident terminal evidence during a pentest?▼

To capture tamper-evident terminal evidence during a pentest, use an evidence-first workflow that wraps every command with timestamps, output, and status markers to ensure auditability and reproducibility of findings.

What is an evidence-chain protocol for terminal operations?▼

An evidence-chain protocol for terminal operations is a structured method that wraps every action with metadata, output, and status markers to create a traceable execution history for post-engagement reporting.

How do I structure session recordings and hashes for penetration test reporting?▼

You structure session recordings and hashes for penetration test reporting by generating standardized evidence files and verifiable execution states that support defensible, auditable documentation of terminal commands.

Can I use a deterministic workflow for reconnaissance and post-exploitation terminal commands?▼

Yes, you can use a deterministic workflow for reconnaissance and post-exploitation by applying a disciplined five-phase process consisting of resolve, read failing surface, execute, verify, and report to guide terminal operations.

What is the best way to ensure traceability of terminal commands during exploitation?▼

The best way to ensure traceability of terminal commands during exploitation is implementing an evidence-first front matter with an action, target, and command chain to maintain a verifiable execution history.