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 v0idOS/performance-deity --skill memorygit clone --depth 1 https://github.com/v0idOS/performance-deityWrote 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/v0idos/performance-deity/memory)<a href="https://agentmods.dev/skills/v0idos/performance-deity/memory"><img src="https://agentmods.dev/badge/skills/v0idos/performance-deity/memory/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/skills/v0idos/performance-deity/memory"><img src="https://agentmods.dev/badge/skills/v0idos/performance-deity/memory.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.00033 | $0.00370 |
| Opus 5.5 | $0.00013 | $0.00148 |
| Sonnet 5.5 | $0.00007 | $0.00074 |
| Haiku 4.5 | $0.00003 | $0.00037 |
Grade A, and why
memory 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 1mo 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
Execute all four phases in order.
Phase 1 — Isolation
- Identify the code suspected of leaking.
- Write a wrapper that runs it in an infinite loop or for ≥1,000,000 iterations.
Phase 2 — Instrumentation
Inject memory tracking into the wrapper:
- Node.js:
process.memoryUsage().heapUsedbefore and after each iteration. - Python:
tracemalloc.start()/tracemalloc.get_traced_memory(). - PowerShell:
[System.GC]::GetTotalMemory($false).
If memory continuously grows without recovering after GC, the leak is confirmed. Show the growth numerically:
Iteration 0: 10 MB
Iteration 100k: 14 MB
Iteration 500k: 40 MB
Phase 3 — Fix
Identify the uncollected reference:
- Event listeners not removed from detached DOM nodes
- Global arrays or caches growing without a size limit
- Closures retaining large outer-scope objects
Apply the fix:
removeEventListenerfor DOM event listenersWeakMap/WeakReffor object-keyed associations that should not prevent GC- Object pooling to reuse memory instead of allocating new objects per cycle
Phase 4 — Report
Re-run the instrumented wrapper and present:
| Metric | Before | After |
|---|---|---|
| Memory growth per 10k ops | +50MB | +0MB |
| GC pause frequency | High | Stable |
Explain the root cause and the specific reference that was being retained.
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.
- 1mo ago First seen · 48 lines · 33 tokens per session scan A bf53f4752961
memory is a skill published in the GitHub repository v0idOS/performance-deity (2 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 370 once invoked, about $0.0001 per session on Opus 5.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
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
shiny-py-optimize
Diagnose and fix performance problems in Shiny for Python apps — slow startup, sluggish interactions, blocking operations, and apps that struggle beyond a handful of concurrent users. Use when a Shiny for Python app is slow, hangs, recomputes too much, times out, or must support more users; when the user asks to…
shiny-r-optimize
Diagnose and fix performance problems in Shiny for R apps — slow startup, sluggish interactions, long-running blocking operations, and apps that struggle beyond a handful of concurrent users. Use when a Shiny app is slow, hangs, recomputes too much, times out, or needs to support more users; when the user asks to…
learn-from-fix
Capture Elixir/Ecto/LiveView lessons and Hex API rules. Use after corrections or when asked to document learning, record a lesson, prevent a fixed mistake, or remember package guidance with --library.
investigate
Find the root cause of Elixir/Phoenix bugs — crashes, exceptions, stack traces, compile errors, LiveView that won't update, silent failures. Use when something is broken or misbehaves. --parallel for 4 tracks.