workflow

A repository rule that directs tasks to the project’s skill-based workflow. It requires reading the main instructions and routing each task to one matching workflow.

In plain words
What is it for?
Use it as the entry point for choosing how to handle a new task in this repository, including requirement checks and workflow selection.
Why use it?
It gives different kinds of work a defined process and prevents unrelated workflows from being mixed together. Larger behavior or contract changes must first have clear requirements.

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/wojisama/skill-based-architecture/workflow
Clone the repo
git clone --depth 1 https://github.com/WoJiSama/skill-based-architecture

Made for: Cursor.

Per session 834 This file is loaded in full into every session.
When invoked 834 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.00834 $0.00834
Opus 5 $0.00417 $0.00417
Sonnet 5 $0.00167 $0.00167
Haiku 4.5 $0.00083 $0.00083

Measured 2d ago against content hash 9363fd739cc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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.

.cursor/rules/workflow.mdc · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cursor Workflow Rule

This repo is the skill-based-architecture meta-skill itself. Formal docs live at repo root. Read SKILL.md first — it is the router.

Quick Routing (survives context truncation)

Task routes live in references/self-hosting-routing.yaml.

For every new task:

  1. Read SKILL.md.
  2. Read references/self-hosting-routing.yaml.
  3. Match exactly one route by labels, trigger_examples, and task intent; if none matches, use other.
  4. Follow only that route's workflow; the route does not preload project knowledge.
  5. Let the workflow inspect the smallest evidence that can decide the next action, then pull later knowledge only when that unresolved decision requires it.

Auto-Triggers

  • New task in same session → always re-match the route above. After a route change, read the new workflow; after compaction, recover only the current workflow and decision-relevant evidence. Only one clear read-only or fixed-contract maintenance action/check with no new desired behavior executes directly. A request that adds or changes user-visible behavior, a business flow/state, or an external contract first reaches requirement-ready; if meaning is incomplete, return current understanding, real risk/conflict, and the minimum normative question without an implementation Plan. Then establish a Task Anchor, prove the current owner and Current -> Target until implementation-ready, and only afterward derive a concise harness-native Plan before mutation. Present only useful alignment, do not repeat visible steps in chat, and run the compact Anchor Checkpoint before each main step. This is Session recitation, not planning-file persistence. Can't tell if context compacted? Re-read the current workflow.
  • Before any requested commit/push/MR/deploy/publish delivery, enter templates/skill/workflows/task-closure.md; Ready for Delivery is not completion, and Closure remains open until the requested artifact is verified.
  • Closure checks fire by blast-radius bucket (path-based classification of files changed):
    • A (entry shells / SKILL.md / routing yaml / scripts / *.tpl) → full AAR + smoke-test + path-integrity gates
    • B (template rules/workflows non-example, references linked from SKILL.md, workflows/full-migration.md) → lightweight AAR only
    • C (README, examples, docs, UPSTREAM-CHANGES, references not linked from SKILL.md) → skip closure entirely
    • Multiple files in one task → take the max bucket. Path not in any list → default B. Trivial edit (typo / whitespace) in an A-bucket file still = full closure (bucket measures what could break, not what changed).
    • Pure Q&A / code explanation / read-only investigation / advice with no file changes → exempt; no AAR, no smoke-test.
    • Full path lists + canonical bucket rules: references/protocols.md § Task Closure Protocol.
  • When adding to templates/ → apply the "would two real projects disagree?" admission test (templates/ANTI-TEMPLATES.md)

Read the full file on GitHub · 42 lines

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. 2d ago First seen · 42 lines · 834 tokens per session scan A 9363fd739cc6

Subscribe to this mod's changes

workflow is a cursor rule published in the GitHub repository WoJiSama/skill-based-architecture (547 stars, last pushed 19d ago), licensed MIT. It adds 834 tokens to every session, about $0.0042 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-30.