{
 "schema_version": 1,
 "generated": "2026-10-20",
 "id": "toolclub-dsh-agent-team-gui--audit-team-token-usage",
 "repo": "toolclub/dsh-agent-team-gui",
 "repo_url": "https://github.com/toolclub/dsh-agent-team-gui",
 "repo_slug": "toolclub-dsh-agent-team-gui",
 "title": "Check how many Tokens a multi-agent run used",
 "page_title": "How to check how many Tokens a multi-agent run used with DSH Agent Team Gui",
 "summary": "Read per-run Token buckets and coverage status in Run Center for planner, member, review, and repair usage.",
 "who": "A developer or team lead who needs to know how much model usage a multi-agent task consumed before running similar work again.",
 "problem": "Multi-agent runs spread usage across planning, members, and review, which makes it hard to tell where Tokens went.",
 "outcome": "A per-run and per-attempt breakdown of uncached input, cache read, cache write, and output Tokens, with coverage marked full, partial, or unavailable.",
 "steps": [
  "Run any team task, or open an existing run in Team runs.",
  "Open the run's usage view and read the four buckets: uncached input, cache read, cache write, and output.",
  "Check the coverage label for the run and for each retry attempt, and note any partial or unavailable entries.",
  "Compare planner, member, review, and repair usage to see which step used the most Tokens.",
  "Do not convert Tokens into money, because the plugin does not guess prices."
 ],
 "agent_prompt": "Using the dsh-agent-team-gui repo, open the Team runs entry for <run-id> and extract the planner, member, review, and repair Token counts with their coverage status. Report a table of the four buckets per step. Verify that any run showing Metering… is reported as pending, not as zero.",
 "agents": [
  "any"
 ],
 "difficulty": "Beginner",
 "time": "30 minutes",
 "basis": "readme",
 "caveat": "Token figures come from provider-reported usage, so runs with partial or unavailable coverage will not show a complete total.",
 "category": "Software and DevOps",
 "tags": [
  "Software and DevOps"
 ],
 "lang": "typescript",
 "requirements": [
  "A working DeepSeek Harness installation with the Web profile, at or above the DSH compatibility version listed in the README install table (>=0.1.5-rc.1)",
  "Node.js and pnpm at the versions listed in the README install table",
  "The dsh-agent-team-gui plugin installed from the README install section",
  "At least one provider/model route configured in DSH"
 ],
 "risk": "none",
 "seen_in_the_wild": false,
 "mentioned_publicly": false,
 "risks": [],
 "best": false,
 "score": 0.8,
 "evidence": [],
 "url": "https://dedupedai.com/use-cases/toolclub-dsh-agent-team-gui/audit-team-token-usage/",
 "md": "https://dedupedai.com/use-cases/toolclub-dsh-agent-team-gui/audit-team-token-usage/index.md",
 "disclaimer": "Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked \"Seen in the wild\", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email hello@dedupedai.com and we will look at it promptly.",
 "api": "https://dedupedai.com/api/v1/usecases/toolclub-dsh-agent-team-gui--audit-team-token-usage.json",
 "api_version": "v1"
}