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/spec-workflow)<a href="https://agentmods.dev/rules/gosha70/code-copilot-team/spec-workflow"><img src="https://agentmods.dev/badge/rules/gosha70/code-copilot-team/spec-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/spec-workflow"><img src="https://agentmods.dev/badge/rules/gosha70/code-copilot-team/spec-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.00025 | $0.01113 |
| Opus 5.5 | $0.00010 | $0.00445 |
| Sonnet 5.5 | $0.00005 | $0.00223 |
| Haiku 4.5 | $0.00003 | $0.00111 |
Grade A, and why
spec-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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Workflow — SDD Specification Protocol
Rules governing when a Software Design Document (SDD) spec is required, what sections it must contain, and how it gates the transition from Plan to Build.
Risk-Based spec_mode Classification
Every planned feature is assigned a spec_mode based on change risk. The Plan agent determines this value and records it in specs/<feature-id>/plan.md YAML frontmatter.
| spec_mode | When to use |
|---|---|
full |
Security changes, schema changes, integration work, features touching more than 2 files |
lightweight |
Features touching 1–2 files, non-critical changes |
none |
Bug fixes (non-security), docs-only changes, trivial or cosmetic changes |
When in doubt, escalate to the next higher mode. Under-speccing a risky change costs more than over-speccing a safe one.
Required Spec Sections per Mode
full
All sections from spec-template.md are required, plus a tasks.md task breakdown:
- User Scenarios
- Requirements
- Constraints / What NOT to Build
- Key Entities
- Success Criteria
tasks.md— discrete, bounded build tasks derived from the spec
lightweight
Only two sections are required in spec.md:
- Requirements
- Constraints
none
No spec.md is required. The Plan agent writes only plan.md.
Plan Approval Gate Protocol
What the Plan Agent Writes
The Plan agent always writes specs/<feature-id>/plan.md regardless of spec_mode. The file must include YAML frontmatter with at minimum:
---
feature_id: <feature-id>
spec_mode: full | lightweight | none
status: draft | approved
origin:
# at least one of: issue, urls, transcripts — OR the explicit
# internal/unrecoverable exemption. See origin-confirmation skill.
issue: <repo>#<number>
urls:
- <external-reference-url>
transcripts:
- specs/<feature-id>/origin/<date>-<slug>.md
origin_claim: |
One paragraph in the user's words quoting their original ask.
---
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 · 121 lines · 25 tokens per session scan A 16948212de92
spec-workflow is a cursor rule published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It adds 25 tokens to every session and 1,113 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
cairn-commit-network
Commits that run cairn hooks need unsandboxed network.
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).