Lens

Claude Code Plugin · Open Source

Stop searching. Start executing.

The AI code assistant market hit $7.4 billion in 2025 — but most tools stop at autocomplete. Lens is a multi-agent orchestrator for Claude Code. /cp plans before building, /cc runs a team of agents in parallel, /cd closes the finished task, and /cs syncs every repo in your workspace.

claude plugin marketplace add livevil7/creeta-lens
claude plugin install lens@CreetaCorp

THE PROBLEM

More plugins. More commands. More confusion.

Claude Code's plugin ecosystem exploded from 0 to 100+ plugins in under a year. That's hundreds of skills, each with different names, different syntax, different specialties.

Can't Find

/review? /code-review? /pr-check? You have the skill installed. You just can't remember what it's called. Multiply that across 12 plugins and 47 skills.

Wrong Pick

You ran /frontend when you needed /code-review. 5 minutes wasted. Wrong picks compound into hours lost per week.

Too Many

10 plugins, 53 commands. You mass-installed the top plugins from the registry, and now your skill list is a maze.

Complex Tasks

You need auth + frontend + review — do you run 3 commands separately? Multi-domain tasks need multiple skills at once.

A DAY WITH LENS

What it feels like — before and after.

Two moments every Claude Code user knows. Lens changes how each one ends.

A feature touches the API, the frontend form, and needs tests — three different specialties.

Without Lens

Run three skills one at a time, copy context between them by hand, and hope nothing slips through.

With Lens

Type /cc. A Leader splits the work, agents run in parallel, and a Supervisor and QA check the result before you see it.

You're about to refactor billing — the kind of change that breaks things quietly.

Without Lens

Start editing and find out what you missed when something downstream fails in production.

With Lens

Type /cp. You get a goal, a Plan A, a Plan B, and a two-model pre-mortem before a single line changes.

WHICH COMMAND?

Ten commands. When to use which.

/cpPlans a task and gets it approved — two grades chosen by risk (default / deep).
/ccParallel task execution engine — decomposes a request into independent sub-tasks, runs them all at once, reviews quality (Supervisor + Codex) and verifies results (QA).
/cdCloses a finished task end to end — merges the task branch, writes the history doc, removes merged branches and their worktrees.
/csMulti-repo git synchronizer — fast-forward pulls incoming work, commits outgoing work on the base branch and pushes it.
/cpsRepo orientation — generates docs/START_HERE.md, an entry point that routes questions to the right doc.
/crLive multi-angle deep research on any topic, reported back with cited sources (URL + date).
/crvPeriodic self-modernization audit — re-evaluates every Lens feature against current Claude Code + Codex capabilities.
/cuScans package managers, VS Code extensions, and Claude Code plugins, and runs auto-risk upgrades.
/ciSyncs this machine's installed plugins to a per-user manifest.
/lens-upgradeOne-stop safe upgrade for the Lens plugin — reinstalls, verifies, and rolls back on failure.

MEET /CC

Parallel Multi-Agent Execution

Complex task? Run a team of agents.

Use /cc when a task spans multiple domains or is too big for one skill. A Leader decomposes the work, Workers run in parallel, a Supervisor reviews quality, and a QA agent verifies — looping until the result holds up.

1

Decompose

The Leader breaks your request into independent, parallelizable sub-tasks.

2

Parallel

Workers — each on the right model — run simultaneously while a Monitor tracks progress.

3

Verify

Supervisor reviews quality and QA tests the result, re-running until every criterion passes.

$/cc build the login API, the form, and tests
→Leader split it into 3 tasks → agents ran in parallel → Supervisor + QA verified → all green.

MEET /CP

Plan-First Execution

Plan before you build.

Use /cp before a big or risky change. It turns a request into a goal-first plan — deliverables, verifiable success criteria, a primary Plan A and a fallback Plan B — then stress-tests it with a dual-model pre-mortem before a single line is written.

1

Goal

Define the deliverable and verifiable success criteria first. The goal is never negotiable — method comes second.

2

Pre-mortem

Claude — and Codex, when installed — independently hunt for holes, feeding the weaknesses straight into Plan B triggers.

3

Execute

Approve, then hand off to /cc. Work loops until every success criterion actually passes.

$/cp refactor the billing module
→Wrote a goal + Plan A/B → Claude & Codex pre-mortem flagged 2 risks → approved, handed to /cc.

MEET /CS

Multi-Repo Sync

Every repo in your workspace. One command.

Use /cs when you juggle many repos. It synchronizes every git repository under your workspace at once — fast-forward pulls, auto-commits dirty trees, pushes ahead. Fail-soft: one repo's problem never blocks the rest.

1

Fetch

Scans every repo under your workspace and fetches origin in a single pass.

2

Sync

Fast-forward pulls when behind, auto-commits dirty trees with a dated message.

3

Push

Pushes ahead commits. Diverged repos are left untouched for a manual resolve.

$/cs
→Scanned every repo → fast-forwarded 3, auto-committed 1 dirty tree, pushed 2 ahead. Diverged ones left for you.

WITH vs WITHOUT

What changes once Lens is in your workspace.

Without Lens

With Lens

Tackle multi-domain work one skill at a time, hand-carrying context.
/cc decomposes it and runs a team of agents in parallel.
Ship big changes, then find the holes in production.
/cp pre-mortems the plan before you build — with Codex as a second reviewer when installed.
Pull and push each repo by hand, one terminal tab at a time.
/cs syncs every repo in one fail-soft pass.

WHY LENS

Why developers keep it installed.

From intent to done — not just a suggestion

Most tools autocomplete a line. Lens plans what you want, spins up a team of agents, and runs it through to a finished result.

One plugin, plan to merge

/cp plans, /cc runs, /cd merges and cleans up, /cs syncs — one plugin carries a task from request to a merged, synced branch.

Quality gates built in

/cc and /cp don't stop at "done." A Supervisor reviews the work and a QA agent actually tests it, looping until every success criterion holds up.

Yours, with no lock-in

MIT licensed and running on your own Claude Code. No Lens account, no walled garden.

FAQ

Questions, answered.

Do I need to configure anything?

Install the plugin and restart Claude Code. Lens has no account or API key of its own, and Codex CLI is optional. One thing to know: /cp only writes plans with the top model (Fable). If your plan does not include it, start Claude Code with LENS_PLANNER_GATE=0.

Does Lens replace Claude Code or my other plugins?

Neither. Lens is a plugin that runs inside Claude Code, alongside the plugins you already have.

What's the difference between /cp and /cc?

/cp writes the plan and gets it approved before anything changes. /cc carries out the work — it decomposes the task and runs a team of agents in parallel. Plan with /cp, build with /cc.

Is it really free?

Yes — MIT licensed and open source. No paid tier and no usage caps from us. You run it on your own Claude Code.

Will /cs touch my git history in ways I don't want?

It only fast-forwards when safe and leaves diverged repos for you to resolve. But /cs push commits uncommitted edits onto the base branch with a dated chore message and pushes them, and git add -A follows your .gitignore — finish or stash work in progress, and skip task branches, before you run it.

GET STARTED

One install. All ten commands included.

Terminal
claude plugin marketplace add livevil7/creeta-lens
claude plugin install lens@CreetaCorp

Requires Claude Code · /cp writes plans with the top model (Fable) — without it, start Claude Code with LENS_PLANNER_GATE=0 · Codex CLI optional

  1. 1Run the install command above
  2. 2Restart Claude Code
  3. 3Type /cp, /cc, or any Lens command followed by what you want

OPEN SOURCE

MIT licensed. Free forever. Built in the open.

Lens is fully open source under the MIT license. In a $7.4 billion market dominated by closed-source tools, we believe the best developer tools should be free and transparent.

MIT
License
100%
Open source
10
Commands

One plugin. Ten commands. From intent to finished task.

Stop juggling commands and repos. Let Lens plan the work, run the agents, close the task, and sync your repos.