claude-usage-limits 1.1.0 → 1.1.1

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "usage-limits",
   "displayName": "Usage Limits",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "Reads how much of your Claude Code usage limit is left, converts it into turns of headroom, and plans the work to fit inside it. Includes a low power switch that keeps spending down even at high effort.",
   "author": {
     "name": "Ridelink",

package/README.md

@@ -100,6 +100,29 @@ git clone https://github.com/ridelink0/claude-code-usage-limits
 Copy-Item -Recurse claude-code-usage-limits\skills\usage-limits "$env:USERPROFILE\.claude\skills\usage-limits"
 ```
 
+One difference between the two: the hook that puts the budget line in front of
+every prompt is declared in the plugin manifest, so it only runs on a plugin
+install. If you took the plain skill and want that behaviour, add it yourself
+in `~/.claude/settings.json`, pointing at wherever you put the skill:
+
+```json
+{
+  "hooks": {
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node \"$HOME/.claude/skills/usage-limits/scripts/brief.js\"",
+            "timeout": 10
+          }
+        ]
+      }
+    ]
+  }
+}
+```
+
 Either way, ask something like "how much usage do I have left" or "can we
 finish this before the limit hits" and Claude will load it. Installed as a
 plugin it also gives you `/usage-limits:check`, which prints the report and

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "claude-usage-limits",
-  "version": "1.1.0",
+  "version": "1.1.1",
   "description": "See how much of your Claude Code usage limit is left as turns of work rather than a percentage, and plan the job to fit inside it.",
   "keywords": [
     "claude",