agentmods.dev

memory-leak-debugging

memory-leak-debugging is a skill for Claude Code, Codex from asgeirtj/system_prompts_leaks. It costs 52 tokens per session (933 once invoked), scanned B, original, CC0-1.0.

A debugging guide for finding memory leaks in JavaScript and Node.js applications. A memory leak occurs when a program keeps data it no longer needs, causing memory use to grow.

In plain words
What is it for?
Use it to investigate browser or server leaks involving detached page elements, event listeners, closures, global values, or unbounded caches.
Why use it?
It helps explain high memory use and out-of-memory crashes by comparing heap snapshots, which record objects held in memory.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 71krepo +384 2d ago B scan 52 tokens original CC0-1.0

Good fit Use it to investigate browser or server leaks involving detached page elements, event listeners, closures, global values, or unbounded caches.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/asgeirtj/system_prompts_leaks/memory-leak-debugging
View source ↗ asgeirtj/system_prompts_leaks
About the project

System Prompts Leaks is a collection of captured system instructions used to guide AI chatbots and coding agents before they receive user messages. It serves researchers and developers studying how different AI assistants are directed.

asgeirtj/system_prompts_leaks · 70,884 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add asgeirtj/system_prompts_leaks --skill memory-leak-debugging
Clone the repo
git clone --depth 1 https://github.com/asgeirtj/system_prompts_leaks

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for memory-leak-debugging

README.md
[![agentmods](https://agentmods.dev/badge/skills/asgeirtj/system_prompts_leaks/memory-leak-debugging/github.svg)](https://agentmods.dev/skills/asgeirtj/system_prompts_leaks/memory-leak-debugging)
Your own site
<a href="https://agentmods.dev/skills/asgeirtj/system_prompts_leaks/memory-leak-debugging"><img src="https://agentmods.dev/badge/skills/asgeirtj/system_prompts_leaks/memory-leak-debugging/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for memory-leak-debugging

Your own site · 80×15
<a href="https://agentmods.dev/skills/asgeirtj/system_prompts_leaks/memory-leak-debugging"><img src="https://agentmods.dev/badge/skills/asgeirtj/system_prompts_leaks/memory-leak-debugging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 933 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.00933
Opus 5.5 $0.00021 $0.00373
Sonnet 5.5 $0.00010 $0.00187
Haiku 4.5 $0.00005 $0.00093

Measured 7d ago against content hash 895127ac55a3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade B, and why

memory-leak-debugging scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

Advanced memory debugging tools (`compare_heapsnapshots`, `get_heapsnapshot_details`, etc.) are only available when the server is started with the `--memoryDebugging` flag. First check if these tools are available; if no
Origin

Copies of this mod

4 near-identical copies found in the catalogue:

Google/antigravity/skills/memory-leak-debugging/SKILL.md · 59 lines

How it starts

The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory Leak Debugging

This skill provides expert guidance and workflows for finding, diagnosing, and fixing memory leaks in JavaScript and Node.js applications using Chrome DevTools MCP tools.

Prerequisites

Advanced memory debugging tools (compare_heapsnapshots, get_heapsnapshot_details, etc.) are only available when the server is started with the --memoryDebugging flag. First check if these tools are available; if not, try to read the MCP configuration file to check if --memoryDebugging is enabled.

Core Principles

  • Prefer MCP memory tools: Do NOT attempt to read raw .heapsnapshot files directly, as they are extremely large and will consume too many tokens. Use the Chrome DevTools MCP heap snapshot tools to summarize, compare, and inspect snapshots.
  • Isolate the Leak: Determine if the leak is in the browser (client-side) or Node.js (server-side).
  • Common Culprits: Look for detached DOM nodes, unhandled closures, global variables, event listeners not being removed, and caches growing unbounded. Note: Detached DOM nodes are sometimes intentional caches; always ask the user before nulling them.
  • Close Loaded Snapshots: Heap snapshots can be large. After completing an investigation, use close_heapsnapshot for each loaded snapshot to release memory held by the MCP server.

Workflows

1. Capturing Snapshots

When investigating a frontend web application memory leak, utilize the chrome-devtools-mcp tools to interact with the application and take snapshots.

  • Use page-scoped tools like click, navigate_page, fill, etc. (specifying pageId) to manipulate the page into the desired state.
  • Revert the page back to the original state after interactions to see if memory is released.
  • Repeat the same user interactions 10 times to amplify the leak.
  • Use take_heapsnapshot (with pageId) to save .heapsnapshot files to disk at baseline, target (after actions), and final (after reverting actions) states.

2. Comparing Snapshots

Read the full file on GitHub · 59 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 59 lines · 52 tokens per session scan B 895127ac55a3

Subscribe to this mod's changes

memory-leak-debugging is a skill published in the GitHub repository asgeirtj/system_prompts_leaks (70,884 stars, last pushed 2d ago), licensed CC0-1.0. It adds 52 tokens to every session and 933 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-30.

Claude CodeDebuggingaianthropicchatbotchatgptclaude
Related

memory-leak-debugging compared with skills from other repositories

memory-leak-debugging next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
memory-leak-debuggingasgeirtj/system_prompts_leaksSkill71k2d agoCC0-1.0B52Claude Code, Codex
hermes-s6-container-supervisionNousResearch/hermes-agentSkill261ktodayMITA20Claude Code, Codex
ast-grepNousResearch/hermes-agentSkill261ktodayMITA16Claude Code, Codex
node-inspect-debuggerNousResearch/hermes-agentSkill261ktodayMITA19Claude Code, Codex
systematic-debuggingNousResearch/hermes-agentSkill261ktodayMITA16Claude Code, Codex
inspecting-hermes-desktop-domNousResearch/hermes-agentSkill261ktodayMITA20Claude Code, Codex
agent-merge-conflict-arbiterNousResearch/hermes-agentSkill261ktodayMITA19Claude Code, Codex