Agent skill

Audit Memory Retention

by ben-manes in ben-manes/caffeine

Analyze reference retention paths that prevent GC of removed entries

Apache-2.0Auto-check passed

Install Audit Memory Retention

skills CLI
$ npx skills add ben-manes/caffeine --skill audit-memory-retention -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ben-manes/caffeine audit-memory-retention --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ben-manes/caffeine.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/audit-memory-retention .claude/skills/audit-memory-retention && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
audit-memory-retention
GitHub stars
18k
Token cost
~572 tokens
SKILL.md length
285 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
Apache-2.0

At a glance

Analyze reference retention paths that prevent GC of removed entries

  • Works in 10 steps: Eviction deques: Can dead nodes remain… → Timer wheel: Are removed nodes always… → Write buffer: Do enqueued tasks hold… → …
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Audit Memory Retention is an agent skill from ben-manes/caffeine. Analyze reference retention paths that prevent GC of removed entries

Its SKILL.md is about 570 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A high performance caching library for Java. The licence is Apache-2.0.

Example prompts

  • “/audit-memory-retention”

Workflow steps

10 steps, taken from the first numbered list in SKILL.md.

  1. Eviction deques: Can dead nodes remain linked? Are key/value/prev/next nulled?
  2. Timer wheel: Are removed nodes always unlinked? Can sentinels retain references?
  3. Write buffer: Do enqueued tasks hold strong references until drained? Upper bound?
  4. Read buffer: Are slots nulled after consumption? Can removed nodes be pinned?
  5. Removal listener queue: Can slow executors cause unbounded retention?
  6. Weak/soft references: After WeakKeyReference is enqueued, is the value still reachable?
  7. Async values: Can removed-but-incomplete futures be pinned via whenComplete?
  8. Cache views/iterators: Can long-lived iterators pin removed entries?
  9. jcache EventDispatcher: per-thread pending synchronous-listener futures —
  10. jcache in-flight futures: does every async path remove its future from

What it can do on your machine

Read from SKILL.md and the folder at commit e972fb0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Audit Memory Retention loads about 572 tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 285 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~572

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ben-manes/caffeine at commit e972fb0, republished under its Apache-2.0 licence (© ben-manes). 285 words, ~572 tokens.

Download SKILL.mdSave it as .claude/skills/audit-memory-retention/SKILL.md (or your agent's skills folder).
name
audit-memory-retention
description
Analyze reference retention paths that prevent GC of removed entries
context
fork
agent
auditor
disable-model-invocation
true

Analyze the cache for memory retention defects — cases where logically removed entries remain reachable through internal data structures.

This is NOT about liveness. Assume the entry IS removed from the CHM. The question is whether internal references still pin the key, value, or node in memory.

Assume at least one retention path exists where removed entries remain reachable longer than necessary. If your analysis yields zero findings, re-examine the write buffer and removal listener queue — explain specifically why retention is bounded.

Trace what happens to references after removal in each data structure:

  1. Eviction deques: Can dead nodes remain linked? Are key/value/prev/next nulled?
  2. Timer wheel: Are removed nodes always unlinked? Can sentinels retain references?
  3. Write buffer: Do enqueued tasks hold strong references until drained? Upper bound?
  4. Read buffer: Are slots nulled after consumption? Can removed nodes be pinned?
  5. Removal listener queue: Can slow executors cause unbounded retention?
  6. Weak/soft references: After WeakKeyReference is enqueued, is the value still reachable? After WeakValueReference is enqueued, is the key still reachable?
  7. Async values: Can removed-but-incomplete futures be pinned via whenComplete?
  8. Cache views/iterators: Can long-lived iterators pin removed entries?
  9. jcache EventDispatcher: per-thread pending synchronous-listener futures — is every publish on a thread paired with awaitSynchronous()/ignoreSynchronous() (or a Quietly variant), including loads running on executor/refresh threads?
  10. jcache in-flight futures: does every async path remove its future from the in-flight set on all completion paths, including exceptional ones?

For each retention path:

  • State the reference chain from GC root to retained object
  • State retention duration (bounded by maintenance? unbounded?)
  • Assess severity: transient vs persistent

Do not report intentional strong references or retention bounded by a single maintenance cycle (unless maintenance can be delayed indefinitely).

© ben-manes, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/audit-memory-retention of ben-manes/caffeine.

Open the folder on GitHubat commit e972fb0

Compare with similar skills

Audit Memory Retention next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Audit Memory Retention compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Memory Retention this skillben-manes/caffeine18k—~572Automated safety check: PassApache-2.0
Culture Retentionsickn33/agentic-awesome-skills47k1 repos~3.8kAutomated safety check: PassMIT
Retently AutomationComposioHQ/awesome-claude-skills77k3 repos~734Automated safety check: PassNone
Dead Code Removercode-yeongyu/oh-my-openagent70k—~1.8kAutomated safety check: PassCustom licence
Rust Path Typesopeninterpreter/openinterpreter69k2 repos~605Automated safety check: PassApache-2.0
Convex Retentionopenclaw/clawhub9.5k—~448Automated safety check: PassMIT

Similar skills

  • Culture Retention

    sickn33/agentic-awesome-skills

    Employee survey and retention register: engagement, growth, happiness, work-life balance and manager-relationship scores, key concern and retention risk.

    47k GitHub starsUsed in 1 repo~3.8k tokens
    Auto-check passed
  • Retently Automation

    ComposioHQ/awesome-claude-skills

    Automate Retently tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~734 tokens
    Productivity & AutomationAuto-check passed
  • Dead Code Remover

    code-yeongyu/oh-my-openagent

    Finds unused code in a TypeScript project, confirms each candidate has no references through the language server, then hands removals to parallel agents.

    70k GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Rust Path Types

    openinterpreter/openinterpreter

    Rules for choosing Rust types for filesystem paths in new Codex code, covering protocol types, internal use and model tool arguments.

    69k GitHub starsUsed in 2 repos~605 tokens
    DevelopmentAuto-check passed
  • Convex Retention

    openclaw/clawhub

    A skill your agent uses when adding or changing ClawHub Convex tables, TTL fields, cleanup crons, retention policy, auth/session cleanup, metric dedupe cleanup, or deprecated table removal

    9.5k GitHub stars~448 tokensUpdated yesterday
    Productivity & AutomationAuto-check passed
  • Remove Bg Automation

    ComposioHQ/awesome-claude-skills

    Automate Remove Bg tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~738 tokens
    Productivity & AutomationAuto-check passed

More from ben-manes/caffeine

All 33 skills in this repo
  • Runs controlled JMH experiments on the Caffeine cache to find shared contention and hot-path waste, then reviews correctness and returns a reviewable patch.

    18k GitHub stars~2.6k tokensUpdated today
    Auto-check: notes
  • Git History Bug Audit

    ben-manes/caffeine

    Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.

    18k GitHub stars~3.3k tokensUpdated today
    Auto-check passed
  • Adversarial Codebase Audit

    ben-manes/caffeine

    Runs a hostile review of the Caffeine Java caching library with parallel subagents that get no design docs, then challenges and consolidates their findings.

    18k GitHub stars~1.9k tokensUpdated today
    Auto-check: notes
  • Caffeine Performance Audit

    ben-manes/caffeine

    Audits the Caffeine cache source for hot-path costs such as allocations, contention and memory layout, reporting only findings tied to specific lines.

    18k GitHub stars~559 tokensUpdated today
    Auto-check passed
  • Audit Sibling Divergence

    ben-manes/caffeine

    Compares code paths that should behave the same, such as sync and async cache methods, and requires a concrete scenario where the two observably disagree.

    18k GitHub stars~4.3k tokensUpdated today
    Auto-check: notes
  • Climber Step Minimization

    ben-manes/caffeine

    Prices each step of the window climber algorithm by disabling it in turn, to find steps that no longer earn their keep and branches that no longer fire.

    18k GitHub stars~3k tokensUpdated today
    Auto-check: notes

Questions about Audit Memory Retention

What does Audit Memory Retention do?

Analyze reference retention paths that prevent GC of removed entries. Audit Memory Retention is an agent skill from ben-manes/caffeine.

How do I install Audit Memory Retention in Claude Code?

Run `npx skills add ben-manes/caffeine --skill audit-memory-retention -a claude-code`. Or copy the skill folder (.claude/skills/audit-memory-retention in ben-manes/caffeine) into .claude/skills/audit-memory-retention in your project. Claude Code loads it when a task matches its description.

How do I install Audit Memory Retention in Codex?

Run `npx skills add ben-manes/caffeine --skill audit-memory-retention -a codex`. Or copy the skill folder (.claude/skills/audit-memory-retention in ben-manes/caffeine) into .agents/skills/audit-memory-retention in your project. Codex loads it when a task matches its description.

Can I use Audit Memory Retention in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ben-manes/caffeine --skill audit-memory-retention -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/audit-memory-retention, .gemini/skills/audit-memory-retention, .github/skills/audit-memory-retention and .opencode/skills/audit-memory-retention in your project.

What does Audit Memory Retention need to run?

SKILL.md names no scripts, command-line tools or credentials: Audit Memory Retention is instructions for the agent only.

Does Audit Memory Retention access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Audit Memory Retention safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Audit Memory Retention use?

Audit Memory Retention is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Audit Memory Retention use?

About 572 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Audit Memory Retention?

Skills that share tags, products or a category with Audit Memory Retention: Culture Retention (sickn33/agentic-awesome-skills, 47k stars), Retently Automation (ComposioHQ/awesome-claude-skills, 77k stars), Dead Code Remover (code-yeongyu/oh-my-openagent, 70k stars) and Rust Path Types (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Memory Retention?

ben-manes (a GitHub user) maintains it in ben-manes/caffeine, which has 17,881 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 9, 2026.

Source: ben-manes/caffeine on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.