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/gosha70/code-copilot-teamWrote 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/rules/gosha70/code-copilot-team/phase-workflow)<a href="https://agentmods.dev/rules/gosha70/code-copilot-team/phase-workflow"><img src="https://agentmods.dev/badge/rules/gosha70/code-copilot-team/phase-workflow/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/rules/gosha70/code-copilot-team/phase-workflow"><img src="https://agentmods.dev/badge/rules/gosha70/code-copilot-team/phase-workflow.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.00020 | $0.02347 |
| Opus 5.5 | $0.00008 | $0.00939 |
| Sonnet 5.5 | $0.00004 | $0.00469 |
| Haiku 4.5 | $0.00002 | $0.00235 |
Grade A, and why
phase-workflow 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase Workflow — Post-Phase Verification
Standardized steps to complete after each build phase, regardless of stack.
Spec Artifact Verification
Post-Plan Verification
After Plan phase completes, verify:
specs/<feature-id>/plan.mdexists withspec_modein YAML frontmatter- If
spec_modeisfullorlightweight:spec.mdexists in the same directory - No unresolved
[NEEDS CLARIFICATION]markers remain inspec.md
Pre-Build Check
Before Build phase starts, verify based on spec_mode:
- full:
spec.mdpresent, no unresolved[NEEDS CLARIFICATION],plan.mdapproved - lightweight:
spec.mdpresent, no unresolved[NEEDS CLARIFICATION],plan.mdapproved - none:
plan.mdpresent and approved — no further spec artifacts required
Phase Completion Integrity
Rules preventing false completion claims. Derived from a real incident where Claude marked a phase complete with major deliverables missing, then suggested experimental work.
No partial completion
Never mark a phase as complete when deliverables are missing. If a phase has two deliverable clusters (e.g., auth middleware + chat UI) and only one is built, the phase is partially complete. Report exactly what is done and what remains.
No summary laundering
When presenting phase status, compare against the latest approved plan/spec (plan.md, spec.md, and tasks.md when present) — not your memory of what was built. If the approved plan says "Auth/RBAC + UI Split into Chat UI and Admin Console" and you only built auth, do not rewrite the summary as "Role-based auth middleware, CORS preflight." Report the gap.
No stretch before core
Never suggest experimental, nice-to-have, or post-plan work when core deliverables from the current or earlier phases are incomplete. If the plan has sequencing prerequisites (e.g., "only pursue after Phase N gates are met"), enforce them.
Regression detection on removal
When existing functionality is removed or replaced during a phase (e.g., replacing a Dash app with FastAPI), verify the replacement is functional before closing the phase. A regression from "working app" to "no app" is a hard blocker — not a separate bug to fix later.
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.
- 1mo ago First seen · 185 lines · 20 tokens per session scan A 58c5aabdbac3
phase-workflow is a cursor rule published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It adds 20 tokens to every session and 2,347 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
02-contributor-guide
Guidelines for contributing new rules or editing existing ones.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).