Preview and verify token-saving coding-harness wiring with Tokless
Preview selected tool and harness configuration, apply Tokless-managed token-saving wiring, and return a versioned diagnostic report across coding agents.
npx skills add agentskillexchange/skills --skill preview-and-verify-token-saving-coding-harness-wiring-with-tokless
Use this workflow when an operator wants a consistent token-saving tool stack across selected existing coding harnesses. The agent detects the operating system and installed harnesses, obtains the operator’s choice of targets and tools, previews Tokless-managed changes, applies the selected setup, and returns a diagnostic report. Invoke it when setup has drifted between harnesses or when moving a known tool selection to another supported harness.
What this skill actually does
Inputs and scope
Collect the target harness IDs, selected tool IDs, operating system, and whether Tokless is already installed. Upstream supports multiple runtimes including Claude Code, Codex and OpenCode. This skill covers selected tool wiring and post-install verification. It does not cover general coding-session orchestration, arbitrary extension marketplace management, or model-provider migration. Keep Headroom proxy routing outside the default path; selecting it requires a separate explicit routing decision.
Install and preview
If the CLI is absent, use the official release assets or upstream installation guide for the operating system. The upstream installer can launch an interactive configuration picker after installation; confirm the chosen harnesses and tools there. Do not silently configure every detected harness. For an existing CLI, record tokless --version and tokless info first.
For example, preview RTK and CodeGraph wiring for Claude Code and Codex with tokless --agents claude,codex --tools rtk,codegraph --dry-run. Replace both lists with the operator’s selections. Review the proposed configuration writes before applying the same command without --dry-run. Let Tokless maintain its managed configuration sections instead of hand-editing their contents.
Verify and return evidence
Run tokless doctor and report the installed version, configured harnesses, selected tools, warnings, and unresolved checks. Use tokless info to identify installation and configuration paths. When CodeGraph is selected, tokless index builds the current project’s index. Treat tokless doctor --fix as a separate interactive repair step; explain the proposed repair before taking it.
Tokless combines curated tools with harness-specific rules, hooks, plugins and MCP entries. Its documented bounded MCP proxy filters exposed tools, while ProjectMem can inject a session-start memory block instead of exposing every read tool. This assembled wiring is the reason to invoke the skill rather than separately installing individual tools. Exact exposed sets can change with upstream versions; use the diagnostic report as the completion evidence.
Completion and rollback
Complete only when the selected targets are configured and diagnostic warnings are resolved or clearly reported. If the operator requests rollback, preview tokless disable --agents claude,codex --dry-run for the relevant targets before applying the scoped disable operation. Keep binary removal separate from unwiring. Do not update all packages or enable proxy routing as incidental cleanup.
Provenance
Reviewed upstream metadata, README, installation guide and CLI dispatch at revision 6294c1d538bac5a8cbaaf47dfbaf4938f74d163f. The exact HoangP8/tokless repository reports 295 stars and 33 forks; latest release v1.0.2 was published on October 19, 2026. These are metadata checks. Runtime installation and security review were not performed during discovery intake.