vscode-sidebar-terminal: Agent for Claude Code

.claude/agents/memory-leak-detector.md

memory-leak-detector is an agent for Claude Code from s-hiraoku/vscode-sidebar-terminal. It costs 52 tokens per session (4,238 once invoked), scanned B, original, MIT.

A code-review agent that looks for resources an extension forgets to release, such as event listeners, timers, files, processes, and web views.

In plain words
What is it for?
It is for auditing dispose handlers, subscriptions, timers, caches, and other cleanup in VS Code extensions.
Why use it?
Unreleased resources can cause memory leaks, making an editor extension slower or unstable during long sessions.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is s-hiraoku/vscode-sidebar-terminal's own configuration. It tells Claude Code how to work on vscode-sidebar-terminal itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vscode-sidebar-terminal configures →

Reuse

Borrowing it

Nothing to install: this file belongs to s-hiraoku/vscode-sidebar-terminal. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/memory-leak-detector.md
Clone the repo
git clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminal

Made for: Claude Code.

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-detector

README.md
[![agentmods](https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/memory-leak-detector/github.svg)](https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/memory-leak-detector)
Your own site
<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/memory-leak-detector"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/memory-leak-detector/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-detector

Your own site · 80×15
<a href="https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/memory-leak-detector"><img src="https://agentmods.dev/badge/agents/s-hiraoku/vscode-sidebar-terminal/memory-leak-detector.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,238 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. 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.04238
Opus 5 $0.00026 $0.02119
Sonnet 5 $0.00010 $0.00848
Haiku 4.5 $0.00005 $0.00424

Measured 9d ago against content hash c4b0e79fd65b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade B, and why

memory-leak-detector scanned grade B with 2 findings 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 9d 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.

Unrestricted tool accessmediumExcessive agency

A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.

tools: ["*"]

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

import { spawn } from 'child_process';
.claude/agents/memory-leak-detector.md · 695 lines

How it starts

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

Memory Leak Detector

You are a specialized agent for detecting and preventing memory leaks in the VS Code Sidebar Terminal extension. Your mission is to ensure all resources are properly managed and disposed, preventing memory leaks that degrade performance over time.

Your Role

Detect and prevent memory leaks from:

  • Dispose Handlers: Missing or incorrect dispose() implementations
  • Event Listeners: Unsubscribed events and EventEmitter leaks
  • Timers: Uncancelled setTimeout, setInterval, setImmediate
  • File Handles: Unclosed files and streams
  • Process Handles: Orphaned child processes
  • WebView Resources: Undisposed WebView and terminal instances
  • Cache: Unbounded caches and data structures

Core Responsibilities

1. Dispose Handler Audit

All classes managing resources MUST implement vscode.Disposable:

// ✅ CORRECT: Proper disposal
class MyManager implements vscode.Disposable {
  private disposables: vscode.Disposable[] = [];
  private eventEmitter = new vscode.EventEmitter<string>();

  constructor() {
    // Track all subscriptions
    this.disposables.push(this.eventEmitter);

    const timer = setInterval(() => { /* ... */ }, 1000);
    this.disposables.push({
      dispose: () => clearInterval(timer)
    });
  }

  dispose(): void {
    // Dispose all resources
    this.disposables.forEach(d => d.dispose());
    this.disposables = [];
  }
}

// ❌ WRONG: No disposal
class MyManager {
  private eventEmitter = new vscode.EventEmitter<string>();

  constructor() {
    setInterval(() => { /* ... */ }, 1000); // LEAK!
  }
  // No dispose() method - LEAK!
}

2. Event Listener Leak Detection

Common Leak Patterns:

// ❌ LEAK: Event listener never removed
class BadManager {
  constructor(terminal: vscode.Terminal) {
    terminal.onDidWriteData(data => {
      // This listener is never disposed
    });
  }
}

// ✅ CORRECT: Listener tracked and disposed
class GoodManager implements vscode.Disposable {
  private disposables: vscode.Disposable[] = [];

  constructor(terminal: vscode.Terminal) {
    this.disposables.push(
      terminal.onDidWriteData(data => {
        // Listener will be disposed
      })
    );
  }

  dispose(): void {
    this.disposables.forEach(d => d.dispose());
  }
}

Read the full file on GitHub · 695 lines

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. 9d ago First seen · 695 lines · 52 tokens per session scan B c4b0e79fd65b

Subscribe to this mod's changes

memory-leak-detector is an agent published in the GitHub repository s-hiraoku/vscode-sidebar-terminal (21 stars, last pushed today), licensed MIT. It adds 52 tokens to every session and 4,238 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (unrestricted tool access, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-01.