Agent skill

Audit Lifecycle

by ben-manes in ben-manes/caffeine

Analyze shutdown, close, and GC-of-cache lifecycle correctness

Apache-2.0Auto-check passed

Install Audit Lifecycle

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

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

GitHub CLI
$ gh skill install ben-manes/caffeine audit-lifecycle --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-lifecycle .claude/skills/audit-lifecycle && 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-lifecycle
GitHub stars
18k
Token cost
~476 tokens
SKILL.md length
219 words
Files
1
Skills in repo
33
Repo updated
First seen
Licence
Apache-2.0

At a glance

Analyze shutdown, close, and GC-of-cache lifecycle correctness

  • Works in 8 steps: Operations racing with close/cleanup:… → Scheduler lifecycle: Does the scheduled… → Executor lifecycle: Reference cycle… → …
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Audit Lifecycle is an agent skill from ben-manes/caffeine. Analyze shutdown, close, and GC-of-cache lifecycle correctness

Its SKILL.md is about 480 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-lifecycle”

Workflow steps

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

  1. Operations racing with close/cleanup: get/put/compute during cleanUp()
  2. Scheduler lifecycle: Does the scheduled future prevent cache GC?
  3. Executor lifecycle: Reference cycle between cache and executor?
  4. Removal listener drain on shutdown: Are pending notifications delivered
  5. In-flight operations during shutdown
  6. Multiple close calls: Is close() idempotent? Concurrent close() corruption?
  7. Finalizer / Cleaner interactions: Reference queues outliving the cache?
  8. jcache manager/cache close: Is teardown symmetric with setup — the OSGi

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 Lifecycle loads about 476 tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 219 words of instructions outside code blocks.

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

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). 219 words, ~476 tokens.

Download SKILL.mdSave it as .claude/skills/audit-lifecycle/SKILL.md (or your agent's skills folder).
name
audit-lifecycle
description
Analyze shutdown, close, and GC-of-cache lifecycle correctness
context
fork
agent
auditor
disable-model-invocation
true

Analyze the cache for defects during shutdown, close, and garbage collection of the cache instance itself.

Assume at least one shutdown or lifecycle race exists. If your analysis yields zero findings, re-examine scheduler/executor lifecycle and in-flight operations during close — explain specifically why no race is possible.

  1. Operations racing with close/cleanup: get/put/compute during cleanUp() or GC? close() state transition? Operations after close()?

  2. Scheduler lifecycle: Does the scheduled future prevent cache GC? Can scheduler fire after cache is collected? Is the task cancelled on close?

  3. Executor lifecycle: Reference cycle between cache and executor? RejectedExecutionException handling when executor is shut down?

  4. Removal listener drain on shutdown: Are pending notifications delivered or dropped? Notifications lost if executor shuts down first?

  5. In-flight operations during shutdown:

    • CacheLoader.load() in progress when cache closes
    • Refresh future's whenComplete callback after close
    • CompletableFuture value pending when cache closes
  6. Multiple close calls: Is close() idempotent? Concurrent close() corruption?

  7. Finalizer / Cleaner interactions: Reference queues outliving the cache? Reference queue processing accessing dead cache?

  8. jcache manager/cache close: Is teardown symmetric with setup — the OSGi context-classloader swap applied on destroy/close as on create/get; in-flight futures awaited; user Closeables (writer, loader, listeners, expiry) closed exactly once under the right classloader?

For each defect: state the lifecycle transition, provide a concrete scenario, state the observable incorrect behavior.

© 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-lifecycle of ben-manes/caffeine.

Open the folder on GitHubat commit e972fb0

Compare with similar skills

Audit Lifecycle 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 Lifecycle compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Audit Lifecycle this skillben-manes/caffeine18k—~476Automated safety check: PassApache-2.0
Prompt Cachingdavila7/claude-code-templates32k6 repos~452Automated safety check: PassMIT
Turborepo Cachingwshobson/agents40k9 repos~2kAutomated safety check: NotesMIT
OmniRoute LLM Cachediegosouzapw/OmniRoute74k1 repos~529Automated safety check: PassMIT
Cachingzebbern/claude-code-guide4.7k—~1.5kAutomated safety check: PassMIT
Content-Hash File Cache Patternaffaan-m/ECC275k5 repos~1.4kAutomated safety check: PassMIT

Similar skills

  • Prompt Caching

    davila7/claude-code-templates

    Caching strategies for LLM prompts including Anthropic prompt caching, response caching, and CAG (Cache Augmented Generation) Use when: prompt caching, cache prompt, response cache, cag, cache…

    32k GitHub starsUsed in 6 repos~452 tokens
    Backend & APIsAuto-check passed
  • Turborepo Caching

    wshobson/agents

    Configures Turborepo pipelines and local or remote caching for monorepo builds, including Vercel remote cache, a self-hosted cache and cache-miss debugging.

    40k GitHub starsUsed in 9 repos~2k tokens
    DevelopmentAuto-check: notes
  • OmniRoute LLM Cache

    diegosouzapw/OmniRoute

    Documents OmniRoute's cache endpoints for reading cache statistics and clearing entries, statistics or the reasoning cache, with notes on TTL and similarity settings.

    74k GitHub starsUsed in 1 repo~529 tokens
    Backend & APIsAuto-check passed
  • Caching

    zebbern/claude-code-guide

    Caching strategies — invalidation, TTL guidelines, cache keys, cache layers, and when not to cache.

    4.7k GitHub stars~1.5k tokensUpdated today
    Backend & APIsAuto-check passed
  • Caches slow file processing results in Python keyed by a SHA-256 hash of the file content, so renames still hit the cache and edits invalidate it automatically.

    275k GitHub starsUsed in 5 repos~1.4k tokens
    DevelopmentAuto-check passed
  • Browser Caching

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Enable browser caching.

    74k GitHub stars~399 tokensUpdated 2 days ago
    Backend & APIsAuto-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 2 days ago
    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 2 days ago
    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 2 days ago
    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 2 days ago
    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 2 days ago
    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 2 days ago
    Auto-check: notes

Questions about Audit Lifecycle

What does Audit Lifecycle do?

Analyze shutdown, close, and GC-of-cache lifecycle correctness. Audit Lifecycle is an agent skill from ben-manes/caffeine.

How do I install Audit Lifecycle in Claude Code?

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

How do I install Audit Lifecycle in Codex?

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

Can I use Audit Lifecycle 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-lifecycle -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-lifecycle, .gemini/skills/audit-lifecycle, .github/skills/audit-lifecycle and .opencode/skills/audit-lifecycle in your project.

What does Audit Lifecycle need to run?

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

Does Audit Lifecycle 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 Lifecycle 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 Lifecycle use?

Audit Lifecycle 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 Lifecycle use?

About 476 tokens (SKILL.md is roughly 1.9k 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 Lifecycle?

Skills that share tags, products or a category with Audit Lifecycle: Prompt Caching (davila7/claude-code-templates, 32k stars), Turborepo Caching (wshobson/agents, 40k stars), OmniRoute LLM Cache (diegosouzapw/OmniRoute, 74k stars) and Caching (zebbern/claude-code-guide, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Audit Lifecycle?

ben-manes (a GitHub user) maintains it in ben-manes/caffeine, which has 17,880 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 6, 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.