stay-within-limits
Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.
Install / Use
npx skills add BuilderIO/skills --skill stay-within-limitsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of stay-within-limits
stay-within-limits scores 87/100 on our quality scale, 2111th of 4,698 Development & Engineering skills we index (top 45%).
Its SKILL.md is 3.3 KB long, split into 6 sections with 2 code examples: a solid amount of guidance for an agent.
With 4,394 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so stay-within-limits is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-29. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
stay-within-limits compared with similar skills
All 4 of these similar skills score higher than stay-within-limits; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| stay-within-limits (this skill)by BuilderIO | 87 | 4.4k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install stay-within-limits?
- Run
npx skills add BuilderIO/skills --skill stay-within-limits. The install tabs above show the steps for each supported agent. - Which AI agents does stay-within-limits work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is stay-within-limits safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is stay-within-limits still maintained?
- The repository was last updated about 2 months ago, so stay-within-limits is actively maintained.
Skill content
View source on GitHubname: stay-within-limits description: Use when long-running or parallel agent work must respect 5-hour and weekly usage limits by checking usage between waves, pausing near the cap, and resuming only when the window is clear.
Stay Within Limits
Keep long-running agent work inside the current 5-hour and weekly usage windows. Check usage before launching substantial work and between waves of parallel subagents. If an active 5-hour or weekly limit is at or above 95%, pause new work until the window is clear enough to continue safely.
Core Loop
- Run a bounded wave of work. Default to at most 3 parallel subagents unless the user or host gives a different throttle.
- Wait for the wave to finish. Do not interrupt in-flight subagents just to save budget; that usually loses work.
- Check current 5-hour and weekly usage with the host's usage/budget tool.
- If either window is at or above 95%, stop launching work and schedule a self-contained resume when the relevant window should clear.
- On resume, re-check the real window or block before continuing. Do not trust elapsed wall-clock time alone.
Usage Signals
Prefer a first-party host usage tool when available. In Claude Code, use:
npx -y ccusage@latest blocks --active --json
Use the JSON to identify the active block start, current cost or percentage, and time remaining. On wake, compare the active block start timestamp with the previous one; a new timestamp is stronger evidence than "enough time passed."
If the tool reports cost instead of a direct percentage, convert through the current account limit when known. For Claude Max-style 5-hour blocks, some users prefer an earlier caution threshold around $500-550; treat that as a user-configured guardrail, not a universal rule. The default stop rule is still 95% of the active 5-hour or weekly limit.
Pausing And Resuming
When a wake/resume tool is available, schedule a wakeup for:
min(3600, secondsUntilWindowClears)
If the runtime clamps wake delays to 60-3600 seconds, chain wakeups for longer waits. Each wakeup should re-check usage, reschedule if still over budget, and continue only when the window is safely below the threshold.
Make wake prompts self-contained. Include:
- The remaining plan.
- The check-then-reschedule rule.
- The 95% threshold and wave throttle.
- The exact usage command or host usage tool to run.
- The previous block/window identifier when available.
- The next verification steps.
- The next wave's handoff packets, including scope, verification commands, and stop conditions, if delegation will resume.
Choosing The Wait Mechanism
- Use a wake/resume tool when the agent needs instructions attached to the future resume.
- Use a background sleep or watcher for fixed timers and things a process can observe directly.
- Use cron or recurring schedules only for recurring fresh-session work.
Avoid short-interval polling for things the host will notify you about, such as background task or subagent completion. For budget pauses, a prompt-cache miss after a long sleep is acceptable; preserving the limit matters more.
Reporting
If you pause, tell the user which window is over threshold, the observed usage, when you scheduled or expect the next check, and what work remains. Keep enough state in the wake prompt that the next turn can resume without relying on conversation momentum.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
