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.
git 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/add-tests)<a href="https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/add-tests"><img src="https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/add-tests/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/add-tests"><img src="https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/add-tests.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00009 | $0.00283 |
| Opus 5.5 | $0.00004 | $0.00113 |
| Sonnet 5.5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
add-tests 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 25d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-tests — 100% identical, 10 lines differ
What it actually says
Context
- Recently modified files: !
git diff --name-only HEAD~3 2>/dev/null | head -10 - Project root files (infer the test framework from these): !
ls -a - Existing test files: !
git ls-files 2>/dev/null | grep -i -e test -e spec | head -10 - Test directory structure: !
ls -la tests/ test/ __tests__/ spec/ 2>/dev/null | head -20
Task
Add tests for the specified target:
- Identify the file/function to test
- Find the corresponding test file (or create one following project conventions)
- Analyze the code to understand:
- Input/output behavior
- Edge cases
- Error conditions
- Write comprehensive tests covering:
- Happy path
- Edge cases
- Error handling
- Run the tests to verify they pass
Target: $ARGUMENTS
If no target specified, focus on recently modified files that lack test coverage.
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.
- 25d ago Changed 3c463afd3a72
- 1mo ago First seen · 33 lines · 9 tokens per session scan A b2f854ff9f37
add-tests is a command published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,420 stars, last pushed 22d ago), licensed MIT. It adds 9 tokens to every session and 283 once invoked, about $0.0000 per session on Opus 5.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
ijfw-audit
Run the IJFW audit gate for the current workflow phase. Usage: /ijfw-audit [phase name].
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
constraints
A command for defining a project's quality standards through a short interview and a written CONSTRAINTS.md file. It records checks, thresholds, exceptions, and commands for enforcing them.
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
analyze-failures
Triage Katalon True Platform/TestOps test failures and file defects. Use when you need to investigate failed test results, classify each failure as product defect vs automation defect vs environment/data issue, cluster failures by common signature, find likely root cause from execution data, and optionally create…