caching-strategy

This skill/documentation implements typical caching patterns and example code for Redis, in-memory, multi-level caches, and HTTP caching. I found no signs of intentional malicious behavior or obfuscation. However, there are several security and operational risks to note: use of Redis KEYS for pattern deletion (should prefer SCAN and chunked deletes), potential accidental caching of sensitive data via naive cache key generation and serialization, unawaited background revalidation that can cause stampedes or missed updates, and unguarded deletion of many keys. These are actionable concerns but not indicators of malware. Recommend: replace KEYS with SCAN, use chunked deletes, sanitize/avoid including secrets in cache keys/values, add locking or single-flight logic for revalidation, and validate object sizes before caching.