khalilmaaouni
UserMeasure Claude Code token use, cut the waste, and prove your savings with a real before and after. Local, private, measured from your own usage counters.
Categories
Indexed Skills (32)
token-shield
Cut Claude Code token spend without cutting quality. This skill should be used when the work involves prompt caching (cache writes, cache hits, TTL, refreshes), deciding between /rewind, /compact, /clear and a fresh session, routing work to the right model tier, pruning plugins and MCP servers that clog the context window, reducing verbose output, or auditing what a session costs. Triggers include tokens, cost, cache, caching, compact, compaction, context full, expensive, spend, budget, token economy, prune plugins.
start
Start a project with a short guided conversation that ends in one clear project brief
help
Explain what BrotherMode does and how to use it, in plain language
next
Recommend the single best next step for the project
status
Show where the project stands right now, in plain language
help
Use when someone asks what BrotherSBE is, how it works, or which command or skill to use. Explains the product in plain language first, points to the three entry skills, and only then offers the full map of specialist skills and commands. Invoke as /brothersbe:help.
next
Use when someone asks what to do next in a BrotherSBE project. Evaluates a fixed priority ladder against observable state and returns exactly one recommended action with a one sentence reason, never a menu of options. Invoke as /brothersbe:next.
review
Use when reviewing a diff, a pull request, or a colleague's change against the design it claims to implement. Runs the deterministic reviewer route to decide who looks, dispatches only the read-only specialists it names, normalizes and deduplicates every finding into the landed schema, and returns a fixed summary (ready or not, mechanical counts, the lenses used, blockers, improvements, pre-existing issues, one next action) with detail underneath. Invoke as /brothersbe:review.
start
Use as the single entry point when someone wants to begin or resume work with BrotherSBE and does not know, or does not care, which command comes next. Detects existing state, resumes it when found, and otherwise asks for the outcome in plain language and routes into kickoff. Invoke as /brothersbe:start.
status
Use when someone wants to know where a BrotherSBE project stands. Wraps the status command and the fence registry, and reframes the raw output as a plain answer with one next action, with technical detail kept below the summary rather than leading it. Invoke as /brothersbe:status.
auto-status
Show where the Full-Auto controller run stands right now, in plain language
auto
Begin or resume the Full-Auto controller, which sequences a signed outcome to a checked deliverable
brief
Ask for the short catch-up on where the work stands, what it cost, and what is waiting on you
decisions
Show the decisions waiting on you, highest stakes first, each with a recommended option
deliver
Package the finished work into one delivery summary with the evidence that it works
handback
Take a decision and the work under it back into your own hands, with nothing lost
stop
Stop the Full-Auto controller run right now, draining in-flight work and releasing every held claim
update
Check the installed version against the newest release and explain how to update, in plain language
handover-pack
Generate the handover pages that let another person take this project over
adopt
Use when installing BrotherSBE into a repository that has not used it before, or when checking whether an existing installation is actually wired up. Inspects the repository for readiness, proposes a configuration, and reports what is present, what is missing and what it could not check. Dry run by default. Invoke as /brothersbe:adopt.
design
Use when the shape of a system is being decided or reviewed: a purpose brief, a process map, an architecture decision record, a technology map, a conceptual to logical to physical data model, diagrams as code, or a verification plan. Runs the six design phases in order, each gating the next, and checks the dossier for the artifacts its tier requires. Invoke as /brothersbe:design.
handover
Use when someone wants to hand this change's ownership to another named human, or when a receiver wants to inspect and accept or reject a handover already prepared for them. Runs the status and worktree checks first, then prepares (or reads) 12-handover.json through the sbe handover engine and renders the concise handover summary a receiver needs, never the project's whole history. Invoke as /brothersbe:handover.
kickoff
Use at the start of any backend, infrastructure, or data engineering task, before designing or writing anything. Classifies the work profile, maps the ground (git state, disk, the repo's own build and test commands), scores the intake into a tier, and names the checks that will verify the work before the work begins. Invoke as /brothersbe:kickoff.
verify
Use when work is about to be called done, a figure that could reach a decision has been produced, a schema migration is part of the change, the change touches money or a partner path, or a verification plan is being written. Runs the hard gates and reports PASS, FAIL or NO-DATA with the evidence each verdict actually read. Invoke as /brothersbe:verify.
work
Use when someone wants BrotherSBE to execute ready plan tasks with implementation workers, not just recommend or design them. Reads the engine's JSON state, briefs and starts one to three independent ready tasks, dispatches each to an implementation-worker subagent inside the worktree sbe work start already opened, verifies the result through sbe work check and sbe work finish, and hands a claimed task to a human on request through the registry's existing shape. Invoke as /brothersbe:work.
review
Check the current work against the definition of done and report what passes and what does not. Use only when the user explicitly asks for a review, an acceptance check, or whether finished work is done; never invoke speculatively just because a change looks complete.
learn
Use when a lesson from an incident, a repeated correction, a review finding or a measured outcome should become a shared rule, or when a session wants to propose an amendment to the laws. Proposes; it never lands a change to shared behavior. Invoke as /brothersbe:learn.
doctor
Check the BrotherMode install itself for problems. Use when the user explicitly asks to check the install, says something seems broken, or right after a fresh install or an update.
view
Write the page that shows where this project stands, and offer it to the user
brothermode
Claude as the founder's colleague and coordinator, adaptive to the nature of each project. Sizes up the work, assigns the right roles, delegates by capability profile with work budgets, keeps one writer per file at a time, speaks to the user in plain outcome-first language, and refuses to call work done without a verifying command run after the last edit. Enforcement is verified on Claude Code only; other runtimes receive advisory instruction files (docs/RUNTIMES.md states what is verified where). Invoke with /brothermode at the start of any project or sizable task.
cursor-dispatch
From Claude Code (Fable or Opus), dispatch a work packet for Cursor to execute under the BrotherMode harness
cursor-execute
Inside Cursor, claim and execute the next BrotherMode harness packet, then return results
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.