<p align="center" <img src="supertool-banner.webp" alt="SuperTool — cut your Claude Code bill by 50%" width="900" </p
supertool
Cut your Claude Code bill by 50%. git-status, but it tells you what to do next.
Saves tokens. Saves money. Saves turns. Works the same in interactive sessions and autonomous runs — humans pair-programming with Claude Code use it every day, not just Kevin-style headless agents. Stdlib only, zero deps, Python 3.9+ — a thin launcher (supertool.py) delegating to one core module (supertool.py) plus the presets, validators, formatters and notifiers you enable per repo.
# 7 ops, 1 round-trip, parallel where safe
supertool 'read:src/Module.py' 'read:src/Auth.py' 'grep:TODO:src/:20' 'map:src/'---
From the same workshop
Four plugins, one team, each does one thing. This one and three siblings:
- claude-remember: memory across sessions. Saves, compresses through Haiku, reloads at the next start.
- claude-jit-context: project knowledge that loads only when the prompt, the file or the tool matches it.
- claude-oss: the maintainer loop that runs these four repos. Triage, build, review, merge, release.
All four install from one marketplace: /plugin marketplace add Digital-Process-Tools/claude-marketplace.
Why supertool
Claude Code's default toolbelt is 1995 unix: cat one file, grep one pattern, git status returns 200 bytes of porcelain, and every tool call re-sends the whole conversation cache at 10% of input price. Supertool ships variants that pack the next question into the current call, so a round-trip bought once does not get bought again.
- git-status — branch, ahead/behind, dirty files, open MR/PR, suggested next step, in one call — every untracked path carrying its own write time so a stray file another process dropped never passes for one you made yourself. Details.
- gh-pr / gl-mr — full PR/MR dashboard: branch, checks, reviews, diff stat, comments, replacing 4-5 raw gh/glab calls, with a summed check tally that never collapses "not all green" into "clean". Details.
- git-worktrees — is an agent already working in this worktree? Branch, occupancy and merge state for every worktree, in three states rather than a guess. Details.
- gh-job / gh-run / gh-branch — a job's failure detail from either GitHub id namespace, a run's job table under a header that sums it, and is this branch green answered for the ref that has no PR after a squash merge. Details. What gh-job:ID:fail actually surfaces about a red leg, measured against six real failed runs on this repository's own history: docs/ci-failure-classification.md.
- gh-prs / gh-issues / gl-mrs — triage boards that rank the queue instead of listing it, and say plainly which population is on screen. Details.
- gh-pr-create / gh-pr-merge / gh-pr-edit — open, merge and correct a pull request with a receipt that proves it landed, not just an exit code. Details.
- gh-issue-create / gh-issue-comment — file and comment with the same published-body read-back, falling back to REST on a GraphQL outage rather than silently duplicating a filing. Details.
- claims:PATH — does a doc's own references — op names, paths, line numbers, cited issues — still hold? Details.
- plugin-marketplace — did a release actually reach anyone installed through the catalogue, or is the pinned commit stale? Details.
- classify:TEXT — is this untrusted text trying to steer an agent? Details.
- statusline — a one-line render for Claude Code's own statusLine hook, joining locally computed segments with fragments a network-backed op (gh-pr today) publishes as a side effect of running normally — the render path itself never calls the network. Details.
That's a sample — supertool ships ~40 ops out of the box (built-ins plus the git / github / gitlab / claude-log presets); add your own and you're past 60 fast. The full pitch, the receipt behind "50%", and why the tool exists at all: docs/philosophy.md.
Install
From the DPT marketplace:
/plugin marketplace add Digital-Process-Tools/claude-marketplace
/plugin install supertool@dpt-plugins