Deputy
Deputize cheap models. Claude stays the sheriff.
Deputy is a Claude Code plugin and MCP server that has a cheap model, DeepSeek V4.1 Flash, review Claude's code for bugs and give second opinions, for under a cent each. Claude keeps writing the code.
claude plugin marketplace add alimohammadiamirhossein/deputy
claude plugin install deputy@deputy
Inside Claude Code the same thing is /plugin marketplace add alimohammadiamirhossein/deputy.
You need uv and a
DeepInfra API key.
What it costs (measured)
| Run | Time | Cost |
|---|---|---|
review: two reviewers check a change with a planted off-by-one bug (both caught it) |
27 s | $0.0011 |
consult: second opinions from 2 angles |
68 s | $0.0018 |
investigate: list a project's functions and their tests |
18 s | $0.0004 |
delegate: fix a bug, add 3 tests, run pytest until green |
46 s | $0.0006 |
Measured on a small demo project with thinking high. On real projects, expect consult and
review to stay under $0.01. Every result shows its real tokens and cost.
What it does
Claude (for example Opus 5.5) stays in charge and writes the code. Deputy adds four tools that run a much cheaper model as a helper inside your project:
| Tool | What it does |
|---|---|
review |
Independent reviewers hunt for bugs in Claude's change before it calls the task done |
consult |
Second opinions from 2–4 angles at once, before Claude commits to a plan |
investigate |
Reads lots of code and returns file:line leads |
delegate |
Hands a coding task to the cheap model (off by default; on request, or in savings mode) |
stats |
Shows roughly how many tokens and dollars Deputy saved: this session, today, this week, all time |
Claude treats everything Deputy says as an unverified hint: it checks each finding against the code and keeps only what holds up.
See what you saved
Every result ends with a one-line estimate, for example from a real investigate run:
Savings (rough): this work would cost about $0.0082 on Claude Opus 5.5; Deputy did it for $0.0001. Saved about $0.0074 and 2.0k Claude Opus 5.5 tokens.
Ask Claude for stats, or run deputy stats, for totals. Reviews and second opinions are listed
separately as extra checks, so they never inflate the savings. The estimate assumes your lead
model would use about as many tokens, so treat it as an order of magnitude. Only numbers are
stored, never code or prompts. Set your lead model with DEPUTY_LEAD_MODEL (opus, sonnet,
haiku, fable or custom).
When to use Deputy, and when not to
Use it for:
- Non-trivial changes where a missed bug costs more than a cent: logic, edge cases, refactors that touch several files.
- A second opinion before Claude commits to a design, without spending Claude tokens on it.
- Wide reading in a big codebase, such as "where is this setting read?".
- Well-specified mechanical work (boilerplate, renames, test scaffolding) in
balancedorsavingsmode, when you want to save Claude tokens.
Skip it for:
- Trivial edits like typos and one-liners. A review takes 30–60 seconds and adds little there.
- Code you may not share with a third party. Deputy sends code to DeepInfra, or to whatever
endpoint you set in
DEPUTY_BASE_URL(a local model works too). - Final answers. Findings come from a weaker model and include false positives, which is why Claude verifies every one.
- Architecture and security-sensitive decisions in
savingsmode. Keep those with Claude.
Quick start
1. Get a DeepInfra API key (DeepInfra hosts DeepSeek's models in the US)
- Sign up at deepinfra.com with GitHub, Google or email.
- In Dashboard → Billing, add a card and $5–10 of credit, then set a spending limit equal to that amount.
- In API Keys, create a key (it starts with
sk-di-) and copy it. Keep it private.
You don't need a plan, a model purchase or a dedicated GPU. Pay-as-you-go credit is enough.
2. Install uv and the plugin
claude plugin marketplace add alimohammadiamirhossein/deputy
claude plugin install deputy@deputy
Claude Code asks for your DeepInfra key and stores it in your system's secure storage.
3. Restart Claude Code and try it
/deputy:review
/deputy:consult I plan to cache sessions in Redis. What am I missing?
/deputy:investigate how does a request reach the database?
Or just work normally: Claude consults and reviews on its own for non-trivial tasks.
Cursor and Codex
One command adds Deputy to the editor's MCP config (with a backup of the old file) and installs the playbook as a Cursor rule or Codex skill:
uvx --from git+https://github.com/alimohammadiamirhossein/deputy deputy setup cursor --project .
uvx --from git+https://github.com/alimohammadiamirhossein/deputy deputy setup codex
Set DEEPINFRA_API_KEY in your environment first, then restart the editor. Add --dry-run to
see the changes without writing them. Ready-made files are in
integrations/.
Other MCP clients (Cline, Windsurf, Claude Desktop)
Deputy is on PyPI as deputy-cc. Add a stdio MCP server
that runs:
uvx deputy-cc serve
with DEEPINFRA_API_KEY set in its environment. Check your setup with uvx deputy-cc doctor.
Recommended model: DeepSeek V4.1 Flash, thinking high
The default is deepseek-ai/DeepSeek-V4.1-Flash-1017 on DeepInfra with thinking set to high.
It's the best price-to-quality option we found for this job:
- Cheap: $0.098 per 1M input tokens and $0.294 per 1M output tokens (October 2026), cheaper than DeepSeek's own API.
- Capable: about 1M tokens of context and reliable tool calling.
- Thinking actually on: DeepInfra leaves its thinking off unless asked. Deputy always asks
(
high), which we confirmed by measuring the reasoning tokens. - Private: DeepInfra says it doesn't train on your data. Your code isn't sent to DeepSeek's own servers.
Modes
| Mode | Who writes the code | Pick it when |
|---|---|---|
| accuracy (default) | Claude, always | You want the best result |
| balanced | Claude; Deputy takes boilerplate | You want some savings without risk |
| savings | Deputy, Claude verifies | You want to save the most tokens |
Change it in the plugin settings (/plugin) or with DEPUTY_MODE.
Learn more
- SKILL.md: the playbook Claude follows (consult → decide → implement → review → check each finding). Also works without the plugin.
- docs/REFERENCE.md: all settings, costs, safety, terms of service, the research behind the design, troubleshooting and the roadmap.
- CHANGELOG.md: what changed in each release.
Deputy stays within Anthropic's rules: Claude Code runs unmodified, and Deputy never touches your Claude login. It's an ordinary MCP tool using your own DeepInfra key.
Support the project
If Deputy caught a bug for you, give it a ⭐ and share it with someone who uses Claude Code. Issues and pull requests are welcome; the good first issues are a good place to start.
MIT © 2026 Amirhossein Alimohammadi · Not affiliated with Anthropic, DeepSeek or DeepInfra.
Keywords: Claude Code plugin, MCP server, Model Context Protocol, AI code review, second opinion, DeepSeek V4.1 Flash, DeepInfra, subagent, Opus, agentic coding, reduce Claude Code cost.
Metadata
Release files for deputy-cc 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| deputy_cc-0.2.0.tar.gz | 168.1 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| deputy_cc-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 205.2 kB
Release files / deputy_cc-0.2.0.tar.gz
| Download URL | deputy_cc-0.2.0.tar.gz |
|---|---|
| Size | 168.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e1f092e808ff5597abbdd304a2907380731126006f4938580b060faba583a664
|
|
BLAKE2b-256 checksum How to use checksums |
bff6f65df1c4499277d793d9ca3613a5530c85f52c20b52e8c10b5c8106578f6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logRelease files / deputy_cc-0.2.0-py3-none-any.whl
| Download URL | deputy_cc-0.2.0-py3-none-any.whl |
|---|---|
| Size | 37.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d0e2d2ad9b738a205c5383f9b5d8dd78710313fefbee99bd02422672c0890c91
|
|
BLAKE2b-256 checksum How to use checksums |
5197f98767dab5df4624d64c389e100b7b9465530e3208e1f9d79f83bb29d815
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for deputy-cc 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for deputy_cc-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.