Agent skill

Cache Policy Hit Rate Comparison

by ben-manes in ben-manes/caffeine

Compares cache eviction policies by hit rate across several cache sizes on a trace file using the Caffeine simulator, with CSV tables and a PNG chart.

Apache-2.0Auto-check: notesDevelopment

Install Cache Policy Hit Rate Comparison

skills CLI
$ npx skills add ben-manes/caffeine --skill sim-compare -a claude-code

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

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

At a glance

Compares cache eviction policies by hit rate across several cache sizes on a trace file using the Caffeine simulator, with CSV tables and a PNG chart.

  • Works in 7 steps: Identify the trace format. Check the… → Select policies to compare. Policy names… → Choose cache sizes. Use a geometric… → …
  • Comparing Caffeine against other eviction policies on a real trace
  • SKILL.md covers Input and Workflow
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

This skill runs a hit-rate comparison of cache policies in the Caffeine simulator for a trace file you provide. It first identifies the trace format from the file extension and contents and from the simulator's reference configuration, using the `format:path` syntax such as `lirs:trace.gz`. It then picks policies named in `category.PolicyName` form, with hyphenated categories, always including the production Caffeine policy, the theoretical optimal and unbounded baselines, LRU, Window TinyLFU and its hill-climbing variant.

Extra competitors are added to suit the trace: recency-heavy, frequency-heavy, scan-resistant or size-aware policies. Cache sizes follow a geometric progression from small values up to near the working set, typically five to eight of them. The run uses the Gradle `simulator:simulate` task with a maximum-size list and the Hit Rate metric, with system properties to override the trace and policies, or `simulator:run` for a single size. Output is one CSV per size, a combined CSV with policies as rows and sizes as columns, and a PNG line chart.

When your agent uses it

  • Comparing Caffeine against other eviction policies on a real trace
  • Choosing which cache sizes to simulate for a given workload
  • Producing hit-rate charts and CSV tables to support a cache tuning decision

Example prompts

  • “Compare policies on the lirs trace in ./traces/ds1.gz across several cache sizes.”
  • “Which eviction policies belong in the comparison for a scan-heavy trace, and which sizes?”
  • “Run the simulator on this trace at a single cache size of 5000 and report the hit rates.”

Requirements

  • A checkout of the Caffeine repository with its Gradle wrapper
  • A cache trace file
  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Bash

Workflow steps

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

  1. Identify the trace format. Check the file extension and contents
  2. Select policies to compare. Policy names use category.PolicyName format.
  3. Choose cache sizes. Use a geometric progression covering the working set
  4. Run the simulation. Use the Gradle task
  5. Read and interpret results. The simulate task produces
  6. Explain findings. For each notable result
  7. Report. Present

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 these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Bash

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    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

Cache Policy Hit Rate Comparison loads about 939 tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 368 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Grep, Glob, Bash

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). 368 words, ~939 tokens.

Download SKILL.mdSave it as .claude/skills/sim-compare/SKILL.md (or your agent's skills folder).
name
sim-compare
description
Run cache policy hit rate comparison across multiple cache sizes with charts
allowed-tools
Read, Grep, Glob, Bash
argument-hint
<trace-file> [policies...] [sizes...]
context
fork
disable-model-invocation
true

Run a comprehensive cache policy comparison for the given trace.

Input

Trace file: $ARGUMENTS

If no policies or sizes are specified, use sensible defaults based on the trace.

Workflow

  1. Identify the trace format. Check the file extension and contents:

    • .gz files: try common formats (lirs, arc, etc.)
    • Look at simulator/src/main/resources/reference.conf for format options
    • Use format:path syntax (e.g., lirs:trace.gz)
  2. Select policies to compare. Policy names use category.PolicyName format. Note: config categories use hyphens (two-queue, greedy-dual), not underscores. Each policy is paired with configured admission filters (default: Always, TinyLfu, Clairvoyant), creating multiple instances per policy name.

    Include at minimum:

    • product.Caffeine (the production implementation)
    • opt.Clairvoyant (theoretical optimal, upper bound)
    • opt.Unbounded (infinite cache, ceiling)
    • linked.Lru (baseline)
    • sketch.WindowTinyLfu (research W-TinyLFU)
    • sketch.HillClimberWindowTinyLfu (adaptive variant)
    • Add relevant competitors based on trace characteristics:
      • For recency-heavy: linked.S4Lru, adaptive.Arc
      • For frequency-heavy: linked.Lfu, irr.Lirs
      • For scan-resistant: two-queue.TwoQueue, two-queue.S3Fifo
      • For size-aware traces: greedy-dual.Gdsf, greedy-dual.Camp
  3. Choose cache sizes. Use a geometric progression covering the working set:

    • Start small (e.g., 100), end near working set size
    • 5-8 sizes: e.g., 100,500,1_000,2_500,5_000,10_000,25_000
    • If the trace has few distinct keys, reduce the range
  4. Run the simulation. Use the Gradle task:

    bash
    ./gradlew simulator:simulate -q \
      --maximumSize=100,500,1000,2500,5000,10000 \
      --metric="Hit Rate" \
      --title="Description" \
      --theme=light \
      --outputDir=build/reports/sim

    Override the trace and policies via system properties appended to the command:

    bash
    -Dcaffeine.simulator.files.paths.0="format:path/to/trace"
    -Dcaffeine.simulator.policies.0=product.Caffeine
    -Dcaffeine.simulator.policies.1=opt.Clairvoyant
    # ... etc

    Note: for single-size runs, use ./gradlew simulator:run -q with -Dcaffeine.simulator.maximum-size=N instead of simulator:simulate.

  5. Read and interpret results. The simulate task produces:

    • Individual CSV per cache size
    • Combined CSV (policies as rows, sizes as columns)
    • PNG chart (line graph of metric vs cache size) Read the CSV output files in the output directory:
    • Compare hit rates across policies at each cache size
    • Identify the crossover points where one policy overtakes another
    • Note the gap between Caffeine and Clairvoyant (theoretical ceiling)
  6. Explain findings. For each notable result:

    • WHY does policy X beat policy Y on this trace?
    • What trace characteristic drives the difference? (frequency bias, recency bias, scan patterns, temporal shifts)
    • How close is Caffeine to optimal? Where does it lose?
    • Reference the relevant research paper if applicable:
      • TinyLFU paper for admission filter behavior
      • Adaptive paper for hill climber effectiveness
      • See .claude/docs/research-foundations.md for paper-to-code mapping
  7. Report. Present:

    • Summary table of hit rates at each cache size
    • Key takeaways (2-3 sentences)
    • Notable policy behaviors
    • Path to generated chart PNG

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

Open the folder on GitHubat commit e972fb0

Compare with similar skills

Cache Policy Hit Rate Comparison 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.

Cache Policy Hit Rate Comparison compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Cache Policy Hit Rate Comparison this skillben-manes/caffeine18k—~939Automated safety check: NotesApache-2.0
Groovy 5 Developer Guideapache/grails-core2.9k—~3kAutomated safety check: PassApache-2.0
Keybase RPC Log Analysiskeybase/client9.3k—~3kAutomated safety check: PassBSD-3-Clause
Performance CheckZeroDeng01/sublinkPro1.7k—~1.8kAutomated safety check: PassMIT
Minecraft CI ReleaseJahrome907/minecraft-agent-skills166—~3.6kAutomated safety check: PassMIT
Releasesol4k/sol4k135—~949Automated safety check: PassApache-2.0

Similar skills

  • Groovy 5 Developer Guide

    apache/grails-core

    Guidance for Groovy 5 work in Grails projects: syntax, closures, traits, DSLs, metaprogramming, Spock tests, static compilation and Java 21 integration.

    2.9k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed
  • Captures a clean Keybase service log and analyzes it for redundant, duplicated or looping RPCs, then checks whether a caching fix reduced the calls.

    9.3k GitHub stars~3k tokensUpdated today
    DevelopmentAuto-check passed
  • Performance Check

    ZeroDeng01/sublinkPro

    Checklist for reviewing code changes that touch queries, APIs, rendering, caching or algorithms for performance, scalability and resource-usage problems.

    1.7k GitHub stars~1.8k tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Minecraft CI Release

    Jahrome907/minecraft-agent-skills

    Set up and review CI, artifact publishing, versioning, and release management for Minecraft 26.x or legacy 1.21.x mods and Paper plugins.

    166 GitHub stars~3.6k tokensUpdated 24 days ago
    DevelopmentAuto-check passed
  • Release

    sol4k/sol4k

    Bump the sol4k library version everywhere, open a release PR, and draft GitHub release notes.

    135 GitHub stars~949 tokensUpdated 9 days ago
    DevelopmentAuto-check passed
  • Guide for writing modern Java 21 in a Grails and Groovy codebase: records, sealed classes, pattern matching, text blocks and how Java works alongside Groovy.

    2.9k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    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 yesterday
    Auto-check: notes

Works with

Categories

Questions about Cache Policy Hit Rate Comparison

What does Cache Policy Hit Rate Comparison do?

Compares cache eviction policies by hit rate across several cache sizes on a trace file using the Caffeine simulator, with CSV tables and a PNG chart. This skill runs a hit-rate comparison of cache policies in the Caffeine simulator for a trace file you provide.gz`.

When should I use Cache Policy Hit Rate Comparison?

Cache Policy Hit Rate Comparison fits situations like: comparing Caffeine against other eviction policies on a real trace; choosing which cache sizes to simulate for a given workload; producing hit-rate charts and CSV tables to support a cache tuning decision.

How do I install Cache Policy Hit Rate Comparison in Claude Code?

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

How do I install Cache Policy Hit Rate Comparison in Codex?

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

Can I use Cache Policy Hit Rate Comparison 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 sim-compare -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sim-compare, .gemini/skills/sim-compare, .github/skills/sim-compare and .opencode/skills/sim-compare in your project.

What does Cache Policy Hit Rate Comparison need to run?

SKILL.md names no scripts, command-line tools or credentials: Cache Policy Hit Rate Comparison is instructions for the agent only. Our summary lists: A checkout of the Caffeine repository with its Gradle wrapper; A cache trace file. Its frontmatter pre-approves these tools: Read, Grep, Glob, Bash.

Does Cache Policy Hit Rate Comparison 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 Cache Policy Hit Rate Comparison safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Cache Policy Hit Rate Comparison use?

Cache Policy Hit Rate Comparison 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 Cache Policy Hit Rate Comparison use?

About 939 tokens (SKILL.md is roughly 3.8k 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 Cache Policy Hit Rate Comparison?

Skills that share tags, products or a category with Cache Policy Hit Rate Comparison: Groovy 5 Developer Guide (apache/grails-core, 2.9k stars), Keybase RPC Log Analysis (keybase/client, 9.3k stars), Performance Check (ZeroDeng01/sublinkPro, 1.7k stars) and Minecraft CI Release (Jahrome907/minecraft-agent-skills, 166 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Cache Policy Hit Rate Comparison?

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.