estimate-token-cost
Skill1 starsChanged 3 months agoMITView on GitHub
Type: skill (deterministic) · Used by: fleet workflows · Status: STUB (P0 scaffold — not yet implemented)
In this repository42 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- k6-browser-testSkill
- k6-load-testSkill
- k6-playwright-converterSkill
- k6-smoke-testSkill
- k6-test-plannerSkill
- apply-ws2-conventionsSkill
- author-resilient-playwrightSkill
- build-status-viewsSkill
- choose-k6-execution-modeSkill
- compare-coreSkill
- compare-to-baselineSkill
- corroborate-2-sourcesSkill
- curate-baselinesSkill
- doc-consistency-checkSkill
- emit-otlp-and-prometheusSkill
- explore-product-structureSkill
- file-perf-regression-jiraSkill
- func-verdictSkill
- heal-playwright-suiteSkill
- k6-profile-benchmarkSkill
- k6-profile-loadSkill
- k6-profile-soakSkill
- k6-profile-spikeSkill
- k6-profile-stressSkill
- learn-via-k6-docsSkill
- link-grafana-panelSkill
- notify-responsible-teamSkill
- open-draft-prSkill
- parse-k6-json-summarySkill
- parse-playwright-summarySkill
- perf-run-logSkill
- run-k6-scriptSkill
- run-ledgerSkill
- run-playwright-suiteSkill
- scope-reviewSkill
- scrub-har-secretsSkill
- triage-func-verdictSkill
- triage-perf-verdictSkill
- verify-k6-scriptSkill
- verify-playwright-suiteSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
When implemented, compute a per-target token ceiling before a fleet fan-out and enforce it: if the projected spend for a target exceeds the …
≈ “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
estimate-token-cost
Compute a per-target token ceiling before fan-out and fail closed when exceeded.
Type: skill (deterministic) · Used by: fleet workflows · Status: STUB (P0 scaffold — not yet implemented)
Prompt
When implemented, compute a per-target token ceiling before a fleet fan-out and enforce it: if the projected spend for a target exceeds the ceiling, FAIL CLOSED for that target rather than overspending.
Apply stage-by-engine routing: pure code for parse / compare / arithmetic / IO; a small model only for narration; a large model only for the reviewer subagent and the fleet cross-check.
Inputs: target count + per-stage engine plan -> Output: per-target ceiling and a go / fail-closed decision per target.
Tools
none — deterministic (plain code)
Data
none
Notes
Activation: P3+. The token-efficiency control Mark asked for. Hard rule: fan-out fails closed — never silently overspend. Most stages must route to pure code; large-model calls are reserved for the reviewer and the cross-check only.
Frozen skill registry: AGENTS.md in this repo
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.