cache-monitor

Name: cache-monitor
Availability: InStock
Author: ybbms

Hash static workspace files with SHA-256 and warn on changes via CLI.

4|Updated Apr 3, 2026

Search Tags:#workspace #hashing #openclaw #prompt-cache #static-layer #cache-monitor

Ready to run

npx skills add https://github.com/ybbms777/openclaw-claude-code-integration --skill cache-monitor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cache-monitor
Source: https://github.com/ybbms777/openclaw-claude-code-integration/tree/main/skills/cache-monitor
Command: npx skills add https://github.com/ybbms777/openclaw-claude-code-integration --skill cache-monitor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill detects when the workspace's static-layer files change, helping ensure prompt cache validity by comparing content hashes and emitting warnings to trigger re-evaluation when needed.

Core Features & Use Cases

Hash verification for core static files (SOUL.md, AGENTS.md, TOOLS.md, USER.md, IDENTITY.md, HEARTBEAT.md, STATIC.md) and persistence of a change log.
Automatic activation during agent/bootstrap startup to guard prompt cache integrity across sessions and hosts.
CLI with --init and --check to initialize state, detect changes, and generate a human-readable report of cache status.

Quick Start

Run the script with --init to initialize hashes, then run it with --check to detect changes and view the report.

Frequently Asked Questions about cache-monitor

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

FAQPage Schema

How do I track static workspace file changes to protect my prompt cache?▼

To track static workspace file changes and protect your prompt cache, you can initialize SHA-256 hashing for core files and run checks to detect modifications. This skill compares content hashes and emits warnings to trigger re-evaluation when static-layer files change.

Why does my prompt cache break across multi-host environments after workspace updates?▼

Your prompt cache breaks across multi-host environments when static-layer files like SOUL.md or IDENTITY.md are modified without detection. Hashing these assets and persisting state guards cache integrity by exposing unauthorized changes during session startup.

How do I initialize and verify static file hashes for workspace auditing?▼

To initialize and verify static file hashes for workspace auditing, run the CLI with --init to establish baseline SHA-256 hashes, then execute --check to compare current states and generate a human-readable report of cache status.

Can I use deterministic file checks for static-layer workspace validation?▼

Yes, you can use deterministic SHA-256 hash checks for static-layer workspace validation. This skill applies fixed checks on a defined set of static files and writes state to a JSON file, ensuring consistent auditing across sessions and hosts.

What limitations exist when monitoring prompt cache integrity with file hashing?▼

A limitation of monitoring prompt cache integrity with file hashing is that it only tracks a fixed set of predefined static files. Dynamic content or files outside the defined static-layer assets are not hashed, meaning unchecked modifications will not trigger cache warnings.

Does cache-monitor work with OpenClaw workspace startup scripts?▼

Yes, cache-monitor works with OpenClaw workspace startup scripts by automatically activating during agent bootstrap. It persists state to the OpenClaw workspace directory, ensuring prompt cache integrity is verified before multi-host sessions begin.