Skills › Superpowers › diagnosing-superpowers › cost-and-time.md
cost-and-time.md
28 lines · skills/diagnosing-superpowers/prompts/cost-and-time.md at 2ce8aa1
Most marks come from matching words in the file, so treat them as pointers.
1Read `prompts/analyst-common.md` first; it gives your role, inputs,
2context-safety rules, and the return format. This file adds the dimension.
4Dimension: Cost and time
6Account for where tokens and wall-clock went.
81. Tokens. Use only the usage records and counter meanings established in the
9 case file. State whether each counter is incremental or cumulative before
10 calculating totals; difference cumulative observations without turning a
11 missing observation into zero. Report the five turns with the largest
12 supported totals and the supported totals per associated session.
132. Wall-clock. Use the evidenced timestamp fields, event boundaries, and units
14 recorded in the case file. Report the five longest supported turns and any
15 gap longer than ten minutes between consecutive events (idle, waiting on an
16 associated session, or waiting on your human partner; say which only when
17 the records show it).
183. Largest tool results: use the case file's evidenced tool-result records to
19 report the ten largest results with their tool and turn. Measure records
20 before extracting bounded content.
214. Compactions: count and locate records whose meaning as compaction events was
22 established during discovery. Report available before/after counters and
23 what the session was doing when each fired; mark unsupported fields absent.
245. Associated sessions: count them and report supported usage, duration, and
25 dispatching turn for each.
266. Report the turns, subagents, tools, or repeats that dominate the
27 totals, with numbers. Do not speculate about why a
28 turn was expensive beyond what the transcript shows.
Read prompts/analyst-common.md first; it gives your role, inputs, context-safety rules, and the return format. This file adds the dimension.
Dimension: Cost and time
Account for where tokens and wall-clock went.
- Tokens. Use only the usage records and counter meanings established in the case file. State whether each counter is incremental or cumulative before calculating totals; difference cumulative observations without turning a missing observation into zero. Report the five turns with the largest supported totals and the supported totals per associated session.
- Wall-clock. Use the evidenced timestamp fields, event boundaries, and units recorded in the case file. Report the five longest supported turns and any gap longer than ten minutes between consecutive events (idle, waiting on an associated session, or waiting on your human partner; say which only when the records show it).
- Largest tool results: use the case file's evidenced tool-result records to report the ten largest results with their tool and turn. Measure records before extracting bounded content.
- Compactions: count and locate records whose meaning as compaction events was established during discovery. Report available before/after counters and what the session was doing when each fired; mark unsupported fields absent.
- Associated sessions: count them and report supported usage, duration, and dispatching turn for each.
- Report the turns, subagents, tools, or repeats that dominate the totals, with numbers. Do not speculate about why a turn was expensive beyond what the transcript shows.
Starts an agent dispatching :25
Starts an agent subagents :26