Stop searching. Start executing.
The AI code assistant market hit $7.4 billion in 2025 — but most tools stop at autocomplete. Lens is a skill navigator AND a multi-agent orchestrator for Claude Code. /c finds and runs the best skill, /cc runs a team of agents in parallel, /cp plans before building, and /cs syncs every repo in your workspace.
THE PROBLEM
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.
/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.
You ran /frontend when you needed /code-review. 5 minutes wasted. Wrong picks compound into hours lost per week.
10 plugins, 53 commands. You mass-installed the top plugins from the registry, and now your skill list is a maze.
You need auth + frontend + review — do you run 3 commands separately? Multi-domain tasks need multiple skills at once.
A DAY WITH LENS
Three moments every Claude Code user knows. Lens changes how each one ends.
You installed a dozen plugins last month. Now you need a code review and can't recall the command.
Without Lens
Scroll through /help, guess between /review, /pr-check, and /code-review, pick the wrong one, lose five minutes.
With Lens
Type /c review my auth changes. Lens scans every plugin, picks the right skill, and runs it.
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.
MEET /C
Single Skill NavigatorUse /c for a focused, single-domain task. Lens reads your request, scans every installed plugin, and runs the single best skill — instantly. No manual searching, no memorizing command names.
Lens inventories every installed plugin and maps all available skills. 12 plugins, 47 skills — all indexed in under 200ms.
AI-powered intent matching analyzes your request against every skill's capabilities. Works in 8 languages.
Select the recommendation and it runs immediately. From request to execution in a single interaction.
MEET /CC
Parallel Multi-Agent ExecutionUse /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.
The Leader breaks your request into independent, parallelizable sub-tasks.
Workers — each on the right model — run simultaneously while a Monitor tracks progress.
Supervisor reviews quality and QA tests the result, re-running until every criterion passes.
MEET /CP
Plan-First ExecutionUse /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.
Define the deliverable and verifiable success criteria first. The goal is never negotiable — method comes second.
Two models — Claude and Codex — independently hunt for holes, feeding the weaknesses straight into Plan B triggers.
Approve, then hand off to /cc. Work loops until every success criterion actually passes.
MEET /CS
Multi-Repo SyncUse /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.
Scans every repo under your workspace and fetches origin in a single pass.
Fast-forward pulls when behind, auto-commits dirty trees with a dated message.
Pushes ahead commits. Diverged repos are left untouched for a manual resolve.
WHICH COMMAND?
/cA focused, single-domain task — find and run the one best skill./ccA complex, multi-domain task — run a team of agents in parallel./cpA big or risky change — plan and pre-mortem before building./csMany repos at once — sync your whole workspace in one pass.WITH vs WITHOUT
Without Lens
With Lens
WHY LENS
Most tools autocomplete a line. Lens reads what you want, picks the right skill or spins up a team of agents, and runs it through to a finished result.
Stop memorizing 50 skill names across a dozen plugins. /c, /cc, /cp, /cs — Lens reads your intent and routes to the right skill for you.
/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.
MIT licensed, zero config, eight languages, running on your own Claude Code. No accounts, no API keys, no walled garden.
FAQ
No. Install the plugin, restart Claude Code, and the four commands work. No config files, no API keys, no signup.
Neither. Lens sits on top of Claude Code and routes to the skills you already have installed — it makes your existing plugins easier to reach.
/c runs the single best skill for a focused, single-domain task. /cc decomposes a multi-domain task and runs a team of agents in parallel. Use /c for one thing, /cc for many.
Yes — MIT licensed and open source. No paid tier and no usage caps from us. You run it on your own Claude Code.
Eight: English, Korean, Japanese, Chinese, Spanish, French, German, and Italian. Type your request in any of them.
No. It only fast-forwards when safe, auto-commits dirty trees with a dated chore message, and leaves diverged repos untouched for you to resolve manually.
GET STARTED
claude plugin marketplace add CreetaCorp/lens && claude plugin install lens@CreetaCorpOPEN SOURCE
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.
Stop juggling commands and repos. Let Lens find the skill, run the agents, plan the work, and sync your repos.