usage-pacing
Skill1 starsChanged 42 days agoMITView on GitHub
Prepare a bounded quota pacing plan when the user asks to maximize tokens, use remaining quota, or pace several coding agents.
In this repository48 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agents.mdcCursor rule
- code-reviewerSkill
- debug-issueSkill
- delegation-coordinatorSkill
- docs-memory-maintainerSkill
- handoffSkill
- human-voice-draftingSkill
- implement-taskSkill
- karpathy-engineerSkill
- local-media-transcriptionSkill
- plan-taskSkill
- pre-edit-checkSkill
- project-plannerSkill
- project-upgraderSkill
- refactor-safelySkill
- self-evaluateSkill
- sharepoint-teams-video-transcript-downloaderSkill
- spec-driven-developmentSkill
- storm-researchSkill
- test-strategistSkill
- update-memory-bankSkill
- upgrade-projectSkill
- code-reviewerSkill
- debug-issueSkill
- delegation-coordinatorSkill
- docs-memory-maintainerSkill
- handoffSkill
- human-voice-draftingSkill
- implement-taskSkill
- karpathy-engineerSkill
- local-media-transcriptionSkill
- plan-taskSkill
- pre-edit-checkSkill
- project-plannerSkill
- project-upgraderSkill
- refactor-safelySkill
- self-evaluateSkill
- sharepoint-teams-video-transcript-downloaderSkill
- spec-driven-developmentSkill
- storm-researchSkill
- test-strategistSkill
- update-memory-bankSkill
- upgrade-projectSkill
- usage-pacingSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
Read usage pacing and use the repository's scripts/usage-pacing.py.
- Distinctive: line 9
Do not resume pacing after a handoff without a new confirmation.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Read usage pacing and use the repository's
scripts/usage-pacing.py. Prepare and explain a concrete plan first. Wait for
separate human confirmation before activation; never confirm your own plan.
Do not resume pacing after a handoff without a new confirmation.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.