A command for temporarily bringing changes from a linked Git worktree into the main worktree for testing. A worktree is a second working folder connected to the same Git repository.

Use it to turn the sharing on or off, refresh the shared changes, or check the current sharing status.

It lets you test worktree changes with the main folder’s installed dependencies, build files, and databases without committing them.

spotlight — Command for Claude Code by sjungling

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.

Clone the repo

git clone --depth 1 https://github.com/sjungling/sjungling-claude-plugins

Made for: Claude Code.

Or install workflow, the plugin that ships this one along with the rest of its 10 commands, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/spotlight/github.svg)](https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/spotlight)

Your own site

<a href="https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/spotlight"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/spotlight/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/spotlight"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/spotlight.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,035 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.01035
Opus 5	$0.00009	$0.00517
Sonnet 5	$0.00003	$0.00207
Haiku 4.5	$0.00002	$0.00103

Measured 9d ago against content hash 577ad4e21d8a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

spotlight 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 9d 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.

plugins/workflow/commands/spotlight.md · 101 lines

How it starts

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

Spotlight testing: merge worktree changes into the main worktree without committing, so you can test in the main worktree's environment (build artifacts, node_modules, databases, etc.).

Parse $ARGUMENTS for the mode: on (default if empty), off, refresh, or status.

Step 1: Detect Environment

Run these commands:

!git rev-parse --show-toplevel !git worktree list !git branch --show-current !git status --porcelain

Determine:

Current worktree path and main worktree path (first entry in git worktree list)
Is this a linked worktree? — current directory is NOT the main worktree
Current branch name
Has uncommitted changes?

If NOT in a linked worktree, abort with:

"Spotlight requires a linked worktree. Run this from a Claude Code worktree, not the main repo."

Step 2: Execute Mode

Mode: `on` (default)

Check main worktree state:
- Run git -C <main-worktree-path> status --porcelain
- If dirty, abort: "Main worktree has uncommitted changes. Commit or stash them first."
- Check for active merge: look for MERGE_HEAD in the main worktree's git directory. For a standard (non-bare) main worktree, check <main-worktree-path>/.git/MERGE_HEAD. If an active merge exists, abort: "Main worktree already has an active merge. Run /spotlight off first."
Checkpoint uncommitted changes (if any):
- If git status --porcelain shows changes:
  - git add -A
  - git commit -m "spotlight: checkpoint"
  - Remember we created a checkpoint commit (report this to user)
- If no changes, skip this step
Merge into main worktree:
- Get current branch name: <branch>
- git -C <main-worktree-path> merge --no-commit --no-ff <branch>
- The --no-ff ensures we get a proper staging even if fast-forward is possible
Handle result:
- Success: Report that changes are now staged in main worktree. Remind user:
  - Test in main worktree at <main-worktree-path>
  - Run /spotlight off when done to clean up
- Conflicts: Report conflicting files. User can resolve in main worktree or run /spotlight off to abort

Read the full file on GitHub · 101 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.

9d ago First seen · 101 lines · 17 tokens per session scan A 577ad4e21d8a

Subscribe to this mod's changes

spotlight is a command published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 25d ago), licensed MIT. It adds 17 tokens to every session and 1,035 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.

Git and workflow

commit

A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.

echoVic/blade-code · 8 tokens

merge-conflict-analysis

You are analyzing merge conflicts for PR #${{ pr-number }}.

rjmurillo/ai-agents · 0 tokens

release-notes

Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.

OpenHands/extensions · 44 tokens

doctor

Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…

doncheli/don-cheli-sdd · 76 tokens

repo-audit

Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.

tractorjuice/arc-kit · 29 tokens

handoff

Export a Waybill Bundle by default, or import one when requested.

wardmos/waybill · 13 tokens