holycodex 0.16.11 → 0.16.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/agent.js +73 -35
- package/dist/assets/plugin/plugin.json +1 -1
- package/dist/assets/plugin/skills/auto-reset/SKILL.md +14 -0
- package/dist/assets/plugin/skills/auto-reset/agents/openai.yaml +6 -0
- package/dist/assets/plugin/skills/session-audit/SKILL.md +12 -0
- package/dist/assets/plugin/skills/session-audit/agents/openai.yaml +6 -0
- package/dist/index.js +101 -55
- package/package.json +2 -2
|
@@ -0,0 +1,14 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: auto-reset
|
|
3
|
+
description: Use when auto-reset is enabled; evaluate quota thresholds and safely use a currently supported banked reset.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Auto reset
|
|
7
|
+
|
|
8
|
+
When the `auto-reset` capability is enabled, Root uses `holycodex-agent auto-reset read` to read fresh usage through the supported local `account/rateLimits/read` RPC and evaluate the returned Codex snapshot. The adapter detects a five-hour limit only from an observed 300-minute window; a weekly-only snapshot identifies a plan without a five-hour window. If quota evidence is missing, do not reset and report what is missing. Specialists never consume a reset credit; only Root owns this consequential action.
|
|
9
|
+
|
|
10
|
+
Continue only when a fresh `holycodex-agent auto-reset consume --idempotency-key <key>` returns a non-`notConsumed` outcome. That adapter rereads quota before acting, checks `availableCount > 0` and a credit row with `resetType: "codexRateLimits"` and `status: "available"`, and calls the typed local `account/rateLimitResetCredit/consume` RPC with that credit id. At an ask-permission threshold, Root first asks the user; only after explicit authorization pass `--authorization granted`. A refusal does not carry into the lower no-permission threshold; if Root tracks the refusal, pass `--authorization refused` on later attempts. Provide a unique idempotency key for each logical attempt and reuse it for retries. Never substitute an unbanked reset. Treat `nothingToReset`, `noCredit`, and `alreadyRedeemed` as exact RPC outcomes and report them.
|
|
11
|
+
|
|
12
|
+
For a plan with a 5-hour limit, Root asks the user before resetting if weekly remaining is below 15% or 5-hour remaining is below 20%. No permission is required if weekly remaining is below 7% or 5-hour remaining is below 15%. For a plan without a 5-hour limit, Root asks before resetting if weekly remaining is below 10%; no permission is required below 5% weekly remaining. Equality does not cross a threshold. Specialists return a required permission decision to Root and never ask the user.
|
|
13
|
+
|
|
14
|
+
A refusal at an ask-permission threshold does not carry forward once the lower no-permission threshold is reached. At that point follow the no-permission threshold, subject to the current supported banked reset mechanism and available quota evidence. Outside the thresholds, do not reset. Report the detected plan limit, measured remaining percentages, threshold applied, permission state, reset outcome, and evidence source without exposing unrelated account data.
|
|
@@ -0,0 +1,12 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: session-audit
|
|
3
|
+
description: Use when session-audit is enabled; explain usage costs and the concrete coordination or harness causes behind them.
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Session audit
|
|
7
|
+
|
|
8
|
+
When the `session-audit` capability is enabled, audit the current Root and every specialist in the session using available rollout, session, and tool evidence.
|
|
9
|
+
|
|
10
|
+
Report request count; input tokens split into cached and uncached input; output and reasoning tokens; and cache rate (cached input divided by total input) when the evidence exposes those values. Identify concrete coordination costs: unnecessary Root turns or cold specialists, duplicate reads, repeated instructions or context, oversized irrelevant tool results, avoidable model decision boundaries or tool calls, avoidable waits or status behavior, and context growth or compaction when relevant.
|
|
11
|
+
|
|
12
|
+
Give each finding its observable evidence, concrete cause, and a specific harness improvement. Separate measured facts from inferences. State which metrics or sessions are unavailable and why; never estimate missing usage or present unavailable data as zero. Raw totals alone do not satisfy an audit.
|