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.

Use it as the entry point for choosing how to handle a new task in this repository, including requirement checks and workflow selection.

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.

workflow — Cursor rule for Cursor by WoJiSama/skill-based-architecture

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.

Clone the repo

git clone --depth 1 https://github.com/WoJiSama/skill-based-architecture

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/wojisama/skill-based-architecture/workflow/github.svg)](https://agentmods.dev/rules/wojisama/skill-based-architecture/workflow)

Your own site

<a href="https://agentmods.dev/rules/wojisama/skill-based-architecture/workflow"><img src="https://agentmods.dev/badge/rules/wojisama/skill-based-architecture/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/wojisama/skill-based-architecture/workflow"><img src="https://agentmods.dev/badge/rules/wojisama/skill-based-architecture/workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 856 This file is loaded in full into every session.

When invoked 856 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00856	$0.00856
Opus 5.5	$0.00342	$0.00342
Sonnet 5.5	$0.00171	$0.00171
Haiku 4.5	$0.00086	$0.00086

Measured 26d ago against content hash 39a4d03f4117, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 26d 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:

Read SKILL.md.
Read references/self-hosting-routing.yaml.
Match exactly one route by labels, trigger_examples, and task intent; if none matches, use other.
Follow only that route's workflow; the route does not preload project knowledge.
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, write user-facing messages in the user's natural language, and explain any internal term in one plain sentence where it appears; 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.

26d ago Changed · +22 tokens per session 39a4d03f4117
1mo 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 (618 stars, last pushed 27d ago), licensed MIT. It adds 856 tokens to every session, about $0.0034 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-30.

agent ai chatbot claude markdown skill

workflow

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Cursor Workflow Rule

Quick Routing (survives context truncation)

Auto-Triggers

What this file has done since we first saw it

Other cursor rules, from other repositories

frontend-theme-guidelines

plugin-rules

handoff

llm-wiki-quality

ponytail

angular-20