check-cache-bugs

Audit Claude Code deployments for cache-related bugs from CC#40524.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/srednoff888-art/4 --skill check-cache-bugs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: check-cache-bugs
Source: https://github.com/srednoff888-art/4/tree/main/examples/skills/check-cache-bugs
Command: npx skills add https://github.com/srednoff888-art/4 --skill check-cache-bugs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit and validate Claude Code setup for cache-related vulnerabilities described in CC#40524, including sentinel handling, resume/continue behavior, and per-session attribution header risks.

Core Features & Use Cases

  • Audits versioned Claude Code components for cache-bug exposure and mitigations.
  • Assesses sentinel configuration, resume/continue handling, and attribution header status across utilities, hooks, commands, and settings.
  • Real-world use: run this skill at session start to verify the environment is free from known cache risks and document mitigations.

Quick Start

Run the check-cache-bugs audit to validate your Claude Code environment before a critical session.

Frequently Asked Questions about check-cache-bugs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What does auditing Claude Code cache integrity involve?

Auditing Claude Code cache integrity involves checking version info, config files, environment variables, and script references to detect sentinel strings, improper resume paths, and attribution header states.

How do I check Claude Code for cache bugs?

You check Claude Code for cache bugs by running an audit that validates versioned components, sentinel configuration, resume/continue handling, and per-session attribution header status across utilities, hooks, commands, and settings.

Why does Claude Code resume continue behavior fail in multi-skill configurations?

Claude Code resume continue behavior may fail due to known cache-related vulnerabilities where artifacts, hooks, and settings improperly influence session caching, requiring an audit to detect improper resume paths.

Can I audit attribution header settings for Claude Code sessions?

You can audit per-session attribution header settings by running checks across environment variables and script references to verify their states and document mitigations for identified risks.

Does the Claude Code cache audit work with local setups?

The Claude Code cache audit is applicable to local setups and multi-skill configurations, enforcing checks across config files and environment variables to verify the environment is free from known cache risks.

When should I run a Claude Code cache vulnerability audit?

You should run a Claude Code cache vulnerability audit at session start before a critical session to verify the environment is free from known cache risks and document mitigations.