preference-cooldown-bypass-bug
CommunitySecure cooldowns by separating preference state.
AuthorHankanman
Version1.0.0
Installs0
System Documentation
What problem does it solve?
The vulnerability arises when rate limiting uses a preference's updatedAt timestamp, allowing users to bypass cooldowns by toggling the preference on and off. This Skill proposes a secure pattern that separates cooldown tracking from the enabled/disabled state.
Core Features & Use Cases
- Separate cooldown storage from the enable/disable flag to ensure toggling never resets cooldowns.
- Migration guidance and concrete code patterns for updating queries and data models.
- Use Case: A messaging system that should throttle messages for each user even if they toggle their notification preference.
Quick Start
Review your current cooldown checks relying on updatedAt, introduce a dedicated cooldown key, migrate data, and run tests to confirm cooldown persistence across preference toggles.
Dependency Matrix
Required Modules
None requiredComponents
Standard package💻 Claude Code Installation
Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.
Please help me install this Skill: Name: preference-cooldown-bypass-bug Download link: https://github.com/Hankanman/claude-config/archive/main.zip#preference-cooldown-bypass-bug Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
Agent Skills Search Helper
Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.