command-logger

Log agent commands with timestamps, session IDs, and results to a local file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a centralized, timestamped audit log for all agent commands, crucial for tracking activity during authorized engagements and for compliance purposes.

Core Features & Use Cases

  • Comprehensive Command Logging: Records every command executed by the agent, including timestamps, session details, command arguments, and execution results.
  • Compliance Ready: Generates logs suitable for auditing and demonstrating agent actions during penetration tests.
  • Forensic Review: Enables detailed post-engagement analysis of agent behavior.

Quick Start

Use the command-logger skill to show me all exec commands run today from the audit log.

Frequently Asked Questions about command-logger

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

FAQPage Schema
How do I create an audit log of all agent commands for compliance reporting?▼

To create an audit log for compliance reporting, you need a tool that records agent commands with timestamps, session IDs, command details, and execution results to a local file for reviewing penetration testing activities.

What is command logging for forensic review in penetration testing?▼

Command logging for forensic review is the process of recording every executed agent command, including arguments and results, to enable detailed post-engagement analysis of agent behavior during authorized security testing.

Can I configure command logging to include tool results and session identifiers?▼

Yes, command logging can be configured to include tool results and session identifiers, allowing you to capture detailed execution data alongside timestamps and command arguments for comprehensive analysis.

How do I retrieve all exec commands run today from a local audit log?▼

To retrieve exec commands run today from a local audit log, query the centralized timestamped log file that records session details and command arguments to filter activities by the current date.

Does centralized command logging work without external dependencies for security auditing?▼

Yes, centralized command logging works without external dependencies by writing timestamped records of agent commands and results directly to a local file, making it suitable for security auditing and compliance.

What are the limitations of using a local file for agent command audit logs?▼

The limitation of using a local file for agent command audit logs is that records are stored locally, which may restrict real-time remote access and centralized aggregation across multiple penetration testing sessions.