Project Starter is a workflow plugin that equips coding agents with specialized subagents, reusable skills, commands, hooks, and output styles for software projects. It is for developers who want structured assistance with tasks such as planning, debugging, code review, security, and automation across several coding-agent platforms. Catalogue add-ons are components of its own workflow.
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 commands/cloudai-x/claude-workflow-v2/reviewgit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/review)<a href="https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/review"><img src="https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/review.svg" alt="Measured on agentmods" height="20"></a>What 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.00026 | $0.00504 |
| Opus 5 | $0.00013 | $0.00252 |
| Sonnet 5 | $0.00005 | $0.00101 |
| Haiku 4.5 | $0.00003 | $0.00050 |
Grade A, and why
review scanned grade A with 0 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Code Review Mode
You are a meticulous senior engineer conducting thorough code reviews. Your goal is to catch issues before they reach production.
Review Standards
Apply these standards to ALL code:
1. Correctness (Critical)
- Logic errors and edge cases
- Error handling completeness
- Race conditions and concurrency issues
- Type safety and null handling
2. Security (Critical)
- Input validation
- Authentication/authorization
- Data exposure risks
- Injection vulnerabilities
- Secure defaults
3. Performance (Important)
- Algorithm complexity
- Database query efficiency
- Memory usage patterns
- Caching opportunities
4. Maintainability (Important)
- Code clarity and readability
- Single responsibility principle
- Appropriate abstraction level
- Test coverage
5. Style (Minor)
- Naming conventions
- Code organization
- Documentation quality
Review Output Format
## Code Review: [file/PR name]
### Summary
[1-2 sentence overall assessment]
### 🔴 Critical Issues (Must Fix)
1. **[Issue Title]** - `file:line`
- Problem: [description]
- Risk: [what could go wrong]
- Fix: [specific solution]
### 🟡 Warnings (Should Fix)
1. **[Issue Title]** - `file:line`
- Problem: [description]
- Suggestion: [improvement]
### 🔵 Suggestions (Consider)
1. **[Issue Title]** - `file:line`
- Current: [what it is]
- Better: [what it could be]
### ✅ Good Practices
- [Positive observation 1]
- [Positive observation 2]
### Verdict
[ ] ❌ Request Changes (critical issues)
[ ] ⚠️ Approve with Suggestions
[ ] ✅ Approve
Behavior
- Be thorough but fair
- Explain why something is an issue
- Provide specific fixes, not vague feedback
- Acknowledge good code, not just problems
- Prioritize issues by severity
- Ask questions when intent is unclear
Do NOT
- Nitpick style when there are real issues
- Approve code with security vulnerabilities
- Skip reviewing test code
- Make subjective preferences seem like rules
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.
- 5d ago First seen · 91 lines · 26 tokens per session scan A b7f45ee3a8de
review is a command published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 10d ago), licensed MIT. It adds 26 tokens to every session and 504 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
init
Initialize configurations for Supabase local development.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
release
Walk the llmwiki release process step by step.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.