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.
npx agentmods add skills/pleaseai/claude-code-plugins/cubic-reviewnpx skills add pleaseai/claude-code-plugins --skill cubic-reviewgit clone --depth 1 https://github.com/pleaseai/claude-code-pluginsWhat 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 | $0.00106 | $0.00645 |
| Opus 5 | $0.00053 | $0.00322 |
| Sonnet 5 | $0.00021 | $0.00129 |
| Haiku 4.5 | $0.00011 | $0.00064 |
Grade B, and why
cubic-review scanned grade B with 2 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 2d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- `curl -fsSL https://cubic.dev/install | bash` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl -fsSL https://cubic.dev/install | bash` How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cubic CLI - AI Code Review
Detect bugs, security issues, and code quality problems in local changes by running cubic review via Bash.
When to Use
- User asks to review code changes, diffs, or branches
- Pre-commit quality checks or bug detection
- Security vulnerability scanning on changed files
- Code style and best practice validation
- Comparing branch changes before creating a PR
Prerequisites
Cubic CLI must be installed. If cubic is not found in PATH, inform the user with installation options:
curl -fsSL https://cubic.dev/install | bashnpm install -g @cubic-dev-ai/cli
Do not run the installation command automatically. Let the user decide.
If cubic returns an authentication error, inform the user to run cubic login or complete browser-based authentication.
CLI Quick Reference
Always pass --json for structured output. Key modes:
cubic review --json-- review uncommitted changes (default)cubic review --base main --json-- compare against a branch (PR-style)cubic review --commit HEAD~1 --json-- review a specific commitcubic review --prompt "focus area" --json-- custom review focus
Constraint:
--base,--commit, and--promptare mutually exclusive.
JSON Output Format
{
"issues": [
{
"priority": "P0",
"file": "src/api/auth.ts",
"line": 45,
"title": "SQL injection vulnerability in user lookup",
"description": "User input is concatenated directly into SQL query without parameterization."
}
]
}
Priority levels: P0 (critical) > P1 (high) > P2 (medium) > P3 (low).
Workflow
- Run
cubic review --json(or with--base/--commitas appropriate) - Parse the JSON output to identify issues
- Sort issues by priority (P0 first)
- For each issue, read the referenced file and line
- Present proposed fixes to the user for approval before applying
- Apply approved fixes using Edit tool
- Re-run
cubic review --jsonto verify fixes
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.
- 2d ago First seen · 69 lines · 106 tokens per session scan B bc5e303cebda
cubic-review is a skill published in the GitHub repository pleaseai/claude-code-plugins (13 stars, last pushed 7d ago), licensed MIT. It adds 106 tokens to every session and 645 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.