focus

A command for choosing which Git repositories—a version-controlled project’s folders—to work on during a session. It shows each repository’s current branch and whether it has uncommitted changes.

In plain words
What is it for?
Use it to switch between projects, select several repositories, or focus on all available repositories except specific ones.
Why use it?
It replaces the previous repository selection so the agent does not accidentally inspect or modify the wrong project. The status details help the user see which work may already be in progress.

Command for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/benkapner/claude-code-basecamp/focus
Clone the repo
git clone --depth 1 https://github.com/Benkapner/claude-code-basecamp

Made for: Claude Code.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 673 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00673
Opus 5 $0.00012 $0.00336
Sonnet 5 $0.00005 $0.00135
Haiku 4.5 $0.00002 $0.00067

Measured 2d ago against content hash aa398f559458, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

focus scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/focus.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Focus Command

Switch repository focus mid-session.

Instructions

Step 1: Scan Available Repositories

# List all git repos in repositories/
for dir in repositories/*/; do
  if [ -d "$dir/.git" ]; then
    name=$(basename "$dir")
    branch=$(git -C "$dir" rev-parse --abbrev-ref HEAD 2>/dev/null || echo "unknown")
    status=$(git -C "$dir" status --porcelain 2>/dev/null)
    if [ -n "$status" ]; then
      count=$(echo "$status" | wc -l | tr -d ' ')
      hint="$branch, $count uncommitted"
    else
      hint="$branch, clean"
    fi
    printf "  %s. %-30s (%s)\n" "$i" "$name" "$hint"
  fi
done

Step 2: Present the Menu

Show the numbered list:

REPOSITORY FOCUS
================
  1. my-project                   (main, clean)
  2. backend-api                  (feature/add-retry, 3 uncommitted)
  3. frontend-app                 (main, clean)

Which repo(s)? (e.g. 1, 1-3, all, all except 2)

If there is a current focus, mark it:

  2. backend-api                  (feature/add-retry, 3 uncommitted)  [current]

Step 3: Apply Selection

The user's response completely replaces the previous focus. Parse their selection:

  • 2 → single repo
  • 1 3 → multiple repos by number
  • 1-3 → range
  • all → all repos
  • all except 2 → all minus specific ones
  • Repo names also work: backend-api

Step 4: Confirm

Focused on: backend-api, frontend-app

Then continue working. Apply the same focus constraint: only read/modify files in the selected repo(s) unless the user explicitly asks otherwise.

Step 5: Update tmux Window Name

If running inside tmux, rename the current window to reflect the focused repo(s):

# Only if inside a tmux session
if [ -n "$TMUX" ]; then
  # Single repo: use repo name
  # Multiple repos: "first-repo+N" where N is the count of additional repos
  tmux rename-window "WINDOW_NAME"
fi

Examples:

  • 1 repo selected → tmux rename-window "backend-api"
  • 3 repos selected → tmux rename-window "backend-api+2"

Read the full file on GitHub · 94 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 94 lines · 23 tokens per session scan A aa398f559458

Subscribe to this mod's changes

focus is a command published in the GitHub repository Benkapner/claude-code-basecamp (16 stars, last pushed 12d ago), licensed MIT. It adds 23 tokens to every session and 673 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.