ram-consumption-verification

Name: ram-consumption-verification
Availability: InStock
Author: tankygranny05

Measure system memory before and after terminating processes with htop in tmux.

2|Updated Jan 30, 2026

Search Tags:#debugging #verification #memory #tmux #process #ram #htop

Ready to run

npx skills add https://github.com/tankygranny05/agent-box --skill ram-consumption-verification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ram-consumption-verification
Source: https://github.com/tankygranny05/agent-box/tree/main/agent-box/seed/claude-skills/ram-consumption-verification
Command: npx skills add https://github.com/tankygranny05/agent-box --skill ram-consumption-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill accurately verifies the RAM consumption of specific processes by measuring system memory before and after their termination, providing a ground truth of actual memory usage.

Core Features & Use Cases

Precise RAM Measurement: Utilizes htop within a tmux session for real-time, system-wide memory reporting, overcoming the limitations of ps or top.
Forceful Process Termination: Employs pkill -9 for reliable killing of target processes based on patterns or PIDs.
Use Case: Debugging memory leaks by confirming how much RAM a suspected process is actually consuming before it's terminated.

Quick Start

Use the ram-consumption-verification skill to measure RAM usage before and after killing processes matching the pattern 'my_script.py', ensuring you clean up the tmux session afterward.

Frequently Asked Questions about ram-consumption-verification

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

FAQPage Schema

How do I verify actual RAM consumption of a process before killing it?▼

You can verify RAM consumption by measuring system memory before and after forceful termination using pkill, utilizing htop in a tmux session for accurate real-time measurement instead of standard ps.

Why does htop in tmux provide better memory measurement than ps for debugging?▼

Htop in tmux provides better memory measurement than ps by offering real-time, system-wide memory reporting that overcomes the limitations of static ps or top outputs during process debugging.

Do I need htop and tmux installed to measure process memory usage this way?▼

Yes, you need htop and tmux installed to measure process memory usage this way, as the verification relies on running htop inside a tmux session and requires knowing the agent's suffix for session naming.

What's the best way to confirm how much RAM a suspected memory leak process is using?▼

The best way to confirm RAM usage of a suspected memory leak is to measure system memory before and after forceful process termination using pkill -9, comparing htop readings to establish ground truth.

How do I forcefully terminate processes by pattern for memory testing?▼

To forcefully terminate processes by pattern for memory testing, use pkill -9 with the target pattern or PID, then compare memory readings from the htop tmux session before and after termination.

When should I clean up the tmux session after measuring RAM usage?▼

You should clean up the tmux session immediately after completing RAM measurement to free system resources, ensuring the htop monitoring session used for verification does not skew memory readings.