Skip to main content
OpenWork uses model tokens when a member actually runs work. Setup actions do not consume tokens by themselves.

​
Know when usage starts

  1. Sending a prompt runs the selected model and consumes tokens. Running a skill does the same because the skill is loaded into the task and the model follows its instructions.
  2. There is no result cache today: rerunning the same task sends a new model request.
  3. Usage scales with the context the agent has to read, including long transcripts, pasted text, file attachments, and tool results.
  4. Tasks that make more tool calls usually cost more because the agent reads results and decides the next step.
  5. Prompt cards do not cost anything while they sit in a policy, no matter how many an admin configures. Installing skills or publishing marketplace plugins also costs nothing until a member runs a task that uses them.
  6. A good skill can reduce cost by making repeat work shorter and more deterministic, with fewer exploratory tool calls.

​
Control spend today

  1. Keep prompt cards short and specific.
  2. Prefer focused skills for repeat workflows.
  3. Attach only the files and transcript context the task needs.
  4. Ask for narrow outputs before broad analysis.
  5. Watch for tasks that loop through many tools, then turn the successful path into a skill.