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.
npx skills add berkcangumusisik/claude-code-practices --skill memory-leakgit clone --depth 1 https://github.com/berkcangumusisik/claude-code-practicesWrote 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/skills/berkcangumusisik/claude-code-practices/memory-leak)<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/memory-leak"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/memory-leak.svg" alt="Measured on agentmods" 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.00021 | $0.00320 |
| Opus 5 | $0.00010 | $0.00160 |
| Sonnet 5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
memory-leak scanned grade A with 0 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 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Memory Leak Analysis
Target: $1 (or src/ if not specified)
Pattern 1: Event Listeners Without Cleanup
// ❌ Listener added but never removed
useEffect(() => {
window.addEventListener('resize', handler)
}, []) // Missing: return () => window.removeEventListener('resize', handler)
Pattern 2: Timers Not Cleared
// ❌ Interval runs forever
setInterval(syncData, 5000)
// ✅ Store ref and clear on unmount
const id = setInterval(syncData, 5000)
return () => clearInterval(id)
Pattern 3: Unbounded Caches
// ❌ Cache grows indefinitely
const cache = new Map()
cache.set(key, value) // never evicted
Pattern 4: Unclosed DB/File Connections
Look for db.connect() without corresponding db.close() in error paths.
For each finding:
- Show the leaking code
- Explain what accumulates and why it matters
- Provide the fix
Rate by severity: Critical (crashes in production under load) / Warning (gradual degradation) / Minor (theoretical).
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.
- 7d ago First seen · 50 lines · 21 tokens per session scan A 618a99901d1b
memory-leak is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (10 stars, last pushed 4mo ago), licensed MIT. It adds 21 tokens to every session and 320 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
check-pipeline
Check that a code and its Pipeline/ .md are still compatible — that every symbol, cell number, data file, and data-flow claim in the pipeline doc still matches the current code (drift detection). Use after editing a documented notebook/engine/script, before trusting a pipeline doc, or on request ("does the pipeline…
reality-check
Re-derive a contested or pushed-back claim in isolation from the definitions, to catch sycophantic capitulation. Use when a result is disputed or you suspect you changed an answer only because the user pushed back.
apply-pipeline
The write-side inverse of /check-pipeline and the pipeline-auditor — read a Pipeline/ doc (and/or an audit report) and EDIT the code accordingly: apply an optimization the pipeline describes, correct code the pipeline (backed by your authoritative notes) shows is wrong, or bring the code in line with the documented…
devharness
Drive and debug a running app via the devharness MCP server - launch or attach to Chrome and Node.js, set breakpoints and logpoints, inspect call stacks and variables, watch console and network, manage dev servers, replay any earlier tool call by its history index, and record reproduction sequences that verify a fix.…
diag
Read-only root-cause diagnosis for a symptom, bug, failure, or unexpected behavior. Establishes the mechanism at file:line and reads up the facts instead of guessing, before any fix is attempted. Produces a diagnosis report; the fix is always a separate step gated by an explicit GO. Use when something is broken…