Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/rhan1/crewline/execute-at-resetgit clone --depth 1 https://github.com/rhan1/crewlineWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00013 | $0.00569 |
| Opus 5 | $0.00006 | $0.00284 |
| Sonnet 5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
execute-at-reset scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Schedule a one-shot execution that fires ~1 minute after the 5h rate limit resets. Use this when /budget-check returns ❌ (won't fit) and the user wants to walk away rather than keep planning.
Task
Schedule execution of: $ARGUMENTS
Procedure
1. Validate the plan file
$ARGUMENTSmust be an absolute file path.- If missing or relative, stop and ask the user to save the plan to a file first (suggest
~/.claude/plans/<name>.md). - Resolve to an absolute path — the scheduled trigger runs later; relative paths could resolve wrong.
2. Read reset time from session state
Read ~/.claude/.session-state.json:
rate_limits.five_hour.resets_at— Unix epoch of next 5h reset
If the cache file is missing or the timestamp >60s stale, stop — don't schedule against stale data.
3. Compute the fire time
- Target epoch =
resets_at + 60(1-minute buffer past reset) - Convert to local time → extract
minute,hour,day-of-month,month - If target minute is 0 or 30, bump by +1 to avoid the global fleet spike (per CronCreate guidance).
- Build cron:
"<min> <hour> <dom> <month> *"
4. Create the trigger
Call CronCreate with:
cron: the expression from step 3prompt:"Execute the plan at <absolute-path>. Read it first, confirm it matches the intent, then work through the steps. Stop and surface anything ambiguous before committing destructive changes."recurring:false(one-shot, auto-deletes after firing)durable:true(persists to disk, survives Claude Code restarts)
5. Confirm to the user
Report:
- 🗓️ Scheduled for:
<local YYYY-MM-DD HH:MM> - 📄 Plan:
<absolute path> - 🆔 Job ID:
<id from CronCreate> - ⚠️ Note: Claude Code must be running for the trigger to fire. The schedule persists across restarts, but a completely closed app means the trigger queues and fires on next start.
- 💡 To cancel:
CronDeletewith the job ID above, or invoke/cancel-scheduled-execution(if built).
6. Length
Keep output under 100 words. One clean confirmation block; no filler.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 53 lines · 13 tokens per session scan A 74b05cad26b3
execute-at-reset is a command published in the GitHub repository rhan1/crewline (2 stars, last pushed 9d ago), licensed MIT. It adds 13 tokens to every session and 569 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.