workflow-bootstrap

A project rule that sets a standard path from planning a change to implementing, testing, reviewing, and releasing it.

In plain words
What is it for?
Use it to coordinate coding roles, require an implementation plan and an explicit ACT decision, and define the handoff through tests, security checks, review, pull requests, and releases.
Why use it?
It prevents code changes from starting before the plan is approved and keeps the work from skipping validation or review steps.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/ymhhh/cursor-implements/workflow-bootstrap
Clone the repo
git clone --depth 1 https://github.com/ymhhh/cursor-implements

Made for: Cursor.

Per session 186 This file is loaded in full into every session.
When invoked 186 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00186 $0.00186
Opus 5 $0.00093 $0.00093
Sonnet 5 $0.00037 $0.00037
Haiku 4.5 $0.00019 $0.00019

Measured yesterday against content hash 854d0003b32b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflow-bootstrap 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 yesterday.

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.

.cursor/rules/workflow-bootstrap.mdc · 17 lines

What it actually says

Workflow bootstrap

Follow the kit entrypoint AGENTS.md (copied with this kit).

Default mainline: plannerIMPLEMENTATION_PLAN.md → user says ACTimplementer → validate (test-runner / code-reviewer / security-auditor / verifier) → pr-author / release-manager.

  • Do not change business code before ACT when a plan is required.
  • Prefer @orchestrator for role chaining prompts; use FE/BE specialist roles as slots.
  • Commit / PR / tech-debt: see skills under .cursor/skills/.
Changes

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.

  1. yesterday First seen · 17 lines · 186 tokens per session scan A 854d0003b32b

Subscribe to this mod's changes

workflow-bootstrap is a cursor rule published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 25d ago), licensed MIT. It adds 186 tokens to every session, about $0.0009 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-31.