Count actions, not vibes.
A search, page load, upload, form fill, model call, and download are separate events. Each receives an ID and a timestamp.
FedPromptly is a practical set of prompts, templates, and habits for seeing what Muse by Meta actually did: action by action, byte by byte, with uncertainty left on the page.
Most “usage” reports collapse a multi-step job into one vague number. This project refuses that shortcut. Define the unit. Capture the evidence. Label the gap.
A search, page load, upload, form fill, model call, and download are separate events. Each receives an ID and a timestamp.
Network bytes and model tokens are different measurements. Keep input, output, reasoning, cache reads, and latency in their own lane.
Measured, reported, estimated, and unavailable are not synonyms. A useful ledger tells the reader which one they are looking at.
Use the same vocabulary in the setup prompt, the interim table, the final report, and the conversation around it.
The included prompt starts in Data Usage Audit Mode. It asks the agent to make a ledger entry before moving to the next action, then surfaces a compact interim table after every five actions.
Here is the shape of the final report. The rows are intentionally plain; the point is to make the evidence hard to hide.
| Action | Type | Target | Sent | Received | Total | Method |
|---|---|---|---|---|---|---|
| A-001 | Search | Search engine | 1.8 KB | 420 KB | 421.8 KB | Estimated |
| A-002 | Open page | example.com | 0 KB | 2.4 MB | 2.4 MB | Measured |
| A-003 | Summarize | Muse model | 12 KB prompt | Token usage separate | N/A | Reported |
| A-004 | Download | report.pdf | 0 KB | 8.1 MB | 8.1 MB | Measured |
Contribute to the documentation, share the prompt with someone running multi-step Muse work, or help fund careful maintenance.
See support options