parsifal1986/tokensburned/connect

Connect TokensBurned

Resolve the plugin root from this skill's location and use node <plugin-root>/bin/burn.js connect.

• Run connection only after the user asks to connect, install, or set up the service.
• Explain that GitHub authorization verifies identity and that one TokensBurned device credential is stored in ~/.burn/credentials.json with user-only permissions.
• Open the server-provided complete verification URL when available so the short code is filled automatically. The user must still verify the displayed code and device name, then explicitly confirm before GitHub authorization. Use the printed short code only as a manual fallback, and never ask them to use a code supplied by someone else.
• Account privacy is stored by the service for the verified GitHub account and inherited on every connected device. Connecting must never reset or reprompt for an existing policy; new accounts start private. Pass --publish-card only when the user explicitly asks to change the account to public and acknowledges that totals, harness/provider/model breakdowns, activity heatmaps, rank, and GitHub identity become public.
• Treat history import as separate consent. Pass --backfill --harness codex in Codex or --backfill --harness claude-code in Claude Code only when the user explicitly asks to import existing history; otherwise pass --no-backfill so a non-interactive harness never imports by implication.
• Pass --all-harnesses only when the user explicitly asks to import every recognized harness and acknowledges the expanded local file scope.
• When history import is approved, state that only aggregate token and request counts, tool/provider/model labels, and activity dates and hours are uploaded; session identifiers stay local. Prompts, replies, tool payloads, source code, repository paths, and transcript files are not uploaded.
• Start background collection with tokensburned run only when the user requests it. Do not add proxies or Git synchronization.