10x CLI
A terminal coding assistant that chains model tiers into multi-step workflows for review, debugging, refactoring, and testing.
- Source repo
- ntegrals/10x
- Stars
- ★ 1.4k
- Last updated
- 8mo ago
- License
- MIT
- Primary language
- TypeScript
- FA score
- 17/100 · Major gaps
At a glance
- Works with
- Portable with changes
- You'll need
- Typical use
- A developer reviewing a file or directory from the terminal can run
/review <path>for security, performance, and style analysis. - Main limitation
- The documentation does not state where to configure an OpenRouter API key, how authentication works, or how costs are controlled.
- Source review
- 17/100 · Major gaps 8 safety controls not found
What does this agent do, and when should you use it?
10x is a coding-assistant CLI installed globally with npm and run from a shell. It offers an interactive session as well as one-shot prompt execution with `-x`. Its Superpowers break complex work into steps that can use different model tiers. Projects can supply context through a root-level `10X.md`, while additional skills and workflows can be defined in `.10x/skills/`, `.10x/superpowers/`, or the corresponding user configuration directories. The documented built-in workflows cover code review, pull-request descriptions, refactoring, debugging, code explanation, and test generation.
Running 10x starts an interactive session, while 10x -x "<prompt>" executes a prompt and exits. /review <path> performs security, performance, and style analysis for a path; /pr generates a PR description from staged or committed changes; /refactor <file> provides analysis and implementation for a refactor; /debug <issue> follows reproduce, analyze, and fix steps; /explain <path> explains code architecture; and /test <file> generates a comprehensive test suite. Custom Superpowers are Markdown files with name and trigger metadata; the shown template passes user input through {{input}}, makes an earlier step’s result available as {{previous}}, and assigns tiers such as fast or smart per step.
- A developer reviewing a file or directory from the terminal can run
/review <path>for security, performance, and style analysis. - An engineer preparing a pull request can run
/prafter staging or committing changes to generate its description. - A maintainer who needs to understand and then modify a source file can use
/refactor <file>for guided analysis and implementation. - A developer investigating a reported defect can use
/debug <issue>to work through reproduction, analysis, and a fix. - A project contributor needing tests for a particular file can run
/test <file>to generate a comprehensive suite.
How do you install or deploy this agent?
In a terminal with npm, run:
npm install -g 10x-cliThen start it with:
10xTo use your own OpenRouter API key, run 10x --byok; the documentation does not specify how that key is configured.
How do you use this agent?
Start an interactive session with 10x. For a one-shot request, use 10x -x "Explain src/app.ts". Select a tier with 10x --model <tier>, where the documented tiers are superfast, fast, and smart; restore a session with 10x --resume <name>. Put project context in a root 10X.md, custom skills in .10x/skills/ and invoke them as /<skill-name>, and custom workflows in .10x/superpowers/.
What are this agent's strengths and limitations?
- It includes concrete commands for review, PR-description generation, refactoring, debugging, explanation, and test generation.
- Superpowers can split a task into multiple steps and assign a different model tier to each step.
- Project- and user-level Markdown skill and workflow directories support team-specific extensions.
- A documented
--byokmode uses an OpenRouter API key supplied by the user.
- The documentation does not state where to configure an OpenRouter API key, how authentication works, or how costs are controlled.
- Its model tiers are named around GPT OSS 20B, Kimi K2 1T, and Claude Opus 4; the source does not document how to add models or providers.
- The “up to 20x faster” statement is a project claim without benchmark methodology, workload conditions, or reproducible results.
- Supported operating systems, Node.js versions, offline behavior, data-handling boundaries, and retry behavior are not documented.
How does this agent compare with similar options?
The README’s feature table compares 10x with Claude Code, Cursor, and GitHub Copilot, positioning 10x around multi-step Superpowers, smart model routing, and BYOK; it does not provide independent performance benchmarks or compatibility detail.
Key facts side by side with the most closely related agents.
| Agent | Source review | Stars | Updated | Language | Full support on |
|---|---|---|---|---|---|
| 10x CLI This agent | 17 · Major gaps | ★ 1.4k | 8mo ago | TypeScript | — |
| Poolside pool | 67 · Some gaps | ★ 426 | 1mo ago | — | OpenAI API |
| git-lrc Commit-Time Code Review | 80 · Good | ★ 1.5k | 7d ago | Go | Claude Code · OpenAI API · Claude API |
| Argot Repository Style Analyzer | 93 · Excellent | ★ 48 | 14d ago | Rust | Claude Code |
How does FollowAgents rate this agent?
Why each dimension lost points
Evidence shows the repository only contains README and package.json, with no documentation or implementation of permission management, user confirmation, data flow transparency, sensitive data handling, dependency security, external effects, rollback, or source attribution. Therefore all trust criteria score 0.
Self-consistency: README claims support for multiple models and features, but package.json does not reflect related dependencies or configuration, indicating inconsistency, score 1. Dependency availability: package.json lists dev dependencies like turbo and typescript, but no runtime dependencies are specified, so availability cannot be confirmed, score 1. Failure messages: No documentation of error handling or failure messages, score 0.
Audience and scenarios: README describes target users and typical use cases (e.g., code review, refactoring), score 1. Capability boundaries: Lists features but does not define boundaries, score 1. Trigger precision: Provides examples of commands and custom triggers, score 1. Environment fit: Explains installation and configuration but lacks system requirements, score 1.
Information architecture: README is well-structured but lacks detailed documentation, score 1. Install notes: Provides npm install command, score 1. Naming stability: Version 0.1.0, no stability promise, score 0. Examples and FAQ: Provides command examples but no FAQ, score 1. Known limitations: Not mentioned, score 0. License: MIT license file present, score 2. Versioning and changelog: No changelog, score 0. Maintenance responsibility: No maintainer or contribution guidelines, score 0.
Output usability: Describes output types (e.g., PR description, test suite) but no actual output examples, score 1. Marginal value: Claims 20x faster than existing tools but no benchmarks, score 1. Cost benefit: BYOK mode may reduce costs but no pricing or comparison, score 1.
Claim traceability: Performance claims lack supporting evidence, score 0. Cross-source corroboration: No external validation, score 0. Fact-inference separation: Does not distinguish facts from inferences, score 0.
- Not found in source: least-privilege scopingGrant only what the task needs: a dedicated account or read-only token, scoped to specific directories and repos.
- Not found in source: confirmation before actingTurn on (or add) a confirmation step before it acts, and try it in a sandbox or test environment before real data.
- Not found in source: data-flow disclosureWatch which external services it contacts (proxy or firewall logs) and keep sensitive data out until you know where it goes.
- Not found in source: sensitive-data handlingUse dedicated, low-privilege, revocable API keys — never production credentials — and keep secrets out of logs.
- Not found in source: dependency securityPin versions and run a dependency audit (npm audit, pip-audit) before installing; prefer running it in a container.
- Not found in source: disclosed external effectsEstablish which external systems it writes to, sends to or changes, and verify with test accounts or repos before production.
- Not found in source: rollback or recovery pathBack up first, or work on a git branch or snapshot, so its changes can be undone.
- Not found in source: verifiable attributionInstall from the official repo or registry and check the publisher and URL to avoid look-alike packages.
- The repository only contains README and package.json, lacking actual code and tests, so functionality cannot be verified.
- Performance claims (20x speedup) are not supported by benchmarks.
- No security-related documentation, such as permissions, data flow, sensitive data handling.
- No changelog or version history, maintenance status unclear.
FAQ
Do I need to provide an API key?
10x --byok for an OpenRouter API key you provide.Can a team create its own workflows?
.10x/superpowers/ can define a trigger command and a multi-step flow using YAML front matter.What does it produce?
Can I continue a previous session?
10x --resume <name> for resuming a session, but the storage location and retention policy are not documented.