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.
Borrowing it
Nothing to install: this file belongs to CloudAI-X/claude-workflow-v2. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/CloudAI-X/claude-workflow-v2/main/CLAUDE.mdgit 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/instructions/cloudai-x/claude-workflow-v2/claude-md)<a href="https://agentmods.dev/instructions/cloudai-x/claude-workflow-v2/claude-md"><img src="https://agentmods.dev/badge/instructions/cloudai-x/claude-workflow-v2/claude-md/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/instructions/cloudai-x/claude-workflow-v2/claude-md"><img src="https://agentmods.dev/badge/instructions/cloudai-x/claude-workflow-v2/claude-md.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.01376 | $0.01376 |
| Opus 5.5 | $0.00550 | $0.00550 |
| Sonnet 5.5 | $0.00275 | $0.00275 |
| Haiku 4.5 | $0.00138 | $0.00138 |
Grade A, and why
claude-workflow-v2 CLAUDE.md scanned grade A with 1 finding 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 24d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- Use subprocess.run with timeout How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Development Guidelines
Team-maintained workflow document. Update frequently with new learnings.
Quick Reference
- Plugin validation:
claude plugin validate . && claude plugin validate .claude-plugin/plugin.json - Test locally:
claude --plugin-dir ./ - Formatting: Prettier for MD/JSON, Black for Python
Development Workflow
Making Changes
-
Before editing any file:
- Run
claude plugin validate . && claude plugin validate .claude-plugin/plugin.jsonto ensure current state is valid - Check existing patterns in similar files
- Run
-
When adding agents (
agents/*.md):- Copy structure from
agents/orchestrator.mdas template - Include "PROACTIVELY" in description for auto-triggering
- Specify tools, model (opus/sonnet/haiku), and skills
- Test trigger keywords work as expected
- Copy structure from
-
When adding skills (
skills/*/SKILL.md):- Keep under 500 lines for optimal context usage
- Include trigger keywords in description
- Make content language-agnostic where possible
-
When adding hooks (
hooks/*):- Register in
hooks/hooks.json - Use
${CLAUDE_PLUGIN_ROOT}for paths - Exit codes: 0 = allow, 2 = block with message
- Test with both success and failure cases
- Register in
-
After all changes:
- Run
claude plugin validate . && claude plugin validate .claude-plugin/plugin.json - Test the specific feature with Claude Code
- Run
Code Conventions
Markdown Files
- Use YAML frontmatter for metadata
- Consistent heading hierarchy (# > ## > ###)
- Code blocks with language specifiers
Python Hooks
- Use
#!/usr/bin/env python3shebang - Read input from stdin as JSON
- Handle all exceptions silently (don't block operations)
- Use subprocess.run with timeout
JSON Files
- 2-space indentation
- No trailing commas
- Validate syntax before committing
Git Workflow
Commit Messages
Follow Conventional Commits:
feat: add new agent for X
fix: correct hook exit code handling
docs: update README with new feature
chore: bump version to X.Y.Z
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.
- 24d ago Changed · +6 lines · +344 tokens per session ba86f73b8106
- 1mo ago First seen · 171 lines · 1,032 tokens per session scan A 34b7ad4881a6
claude-workflow-v2 CLAUDE.md is an instructions file published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,420 stars, last pushed 21d ago), licensed MIT. It adds 1,376 tokens to every session, about $0.0055 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
data-scientist copilot-instructions.md
Repository instructions for a data-science workflow in GitHub Copilot, covering datasets, statistics, and analysis files.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).