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.
curl -O https://raw.githubusercontent.com/s-hiraoku/vscode-sidebar-terminal/main/.claude/agents/memory-leak-detector.mdgit clone --depth 1 https://github.com/s-hiraoku/vscode-sidebar-terminalWrote 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.
[](https://agentmods.dev/agents/s-hiraoku/vscode-sidebar-terminal/memory-leak-detector)<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.
<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>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.
| Model | Per session | Once 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 |
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'; 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());
}
}
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.
- 9d ago First seen · 695 lines · 52 tokens per session scan B c4b0e79fd65b
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.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.