JetBrains

Benjamin Plus Skill — Development skill for Claude Code

Development community

Benjamin-Plus: a measured token-efficiency skill for coding agents (−17.9% cost median, quality unchanged).

How to install Benjamin Plus Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open JetBrains/benjamin-plus-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Benjamin Plus Skill does

Benjamin-Plus: a measured token-efficiency skill for coding agents (−17.9% cost median, quality unchanged). Inject it, don't install it.

Alternatives in Development

  • Pi — PI Wisdom-in-Action Engine v23 — top mandates, scene router, delivery quality gates, anti-patterns, battle mom 107 ★
  • Claude Architect — A plug-and-play framework for generating projects with Claude Code CLI — optimized for speed, token efficiency 74 ★
  • Decant — Local-first analysis of Claude Code and Codex sessions: token spend, context windows, files touched, and cost 59 ★

README

Benji — the benjamin-plus mascot

“Beware of little expenses; a small leak will sink a great ship.”
— Benjamin Franklin

benjamin-plus

A token-efficiency skill for coding agents.
It changes how the agent looks things up and waits — never what it builds.

Measured: up to −18 % cost and −22 % tokens per task, quality unchanged.


What the skill teaches

An agent pays twice for every clumsy lookup: once for the step itself, and again every time the growing conversation gets re-read. So the skill teaches five habits:

  1. Recon in one pass. Gather the facts up front in one combined step instead of poking at the repo five separate times. And before copying a format or convention, look at two real examples, not one.
  2. Keyhole reads. When the agent only needs to see something, it reads 50 lines, not the whole file. Data it will actually transform is never truncated.
  3. Probe the environment once. Check every dependency in one command and install whatever is missing in one go, instead of discovering them one crash at a time.
  4. Green means the task's own check. If the task says how to verify, that command is the definition of done. A missing compiler is still the agent's problem to fix, and a check that fails twice means the approach is wrong, not the symptom. When it passes: stop.
  5. Polling is a step. A build that hasn't finished has nothing new to say. Check on it every 30 seconds, not every second. On some agent platforms, polling alone turned out to be nearly half of all steps.

The skill's full text: [`RULESET.md`](RULESET.md) (~745 tokens injected).

What to expect

![Median paired savings across six metrics](assets/savings.svg)

![Token consumption by arm](assets/tokens.svg)

  • Quality unchanged. 7 better / 5 worse / 6