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/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/skill-workflows)<a href="https://agentmods.dev/rules/kensaurus/cursor-kenji/skill-workflows"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/skill-workflows/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/kensaurus/cursor-kenji/skill-workflows"><img src="https://agentmods.dev/badge/rules/kensaurus/cursor-kenji/skill-workflows.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.00033 | $0.00393 |
| Opus 5.5 | $0.00013 | $0.00157 |
| Sonnet 5.5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00039 |
Grade A, and why
skill-workflows 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 23d 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.
What it actually says
Skill Routing Index
A request that spans phases (spec, build, test, ship) goes to a bundled workflow skill, not a chain of single-phase skills. Where a name misleads:
- An approved plan with open items or deferrals →
complete-everything; a mechanical change stopped short of 100% →burndown-full; list parked work in BACKLOG.md without doing it →housekeep-backlog. - Raw feedback (reports, reviews, Sentry, QA, audits) → deduplicated tickets,
each closed →
workflow-feedback-to-closure; a ranked fix loop on a live app's signals →iterate-post-launch. - Prove tools, installs, services, and verify commands before a long run →
workflow-environment-ready; checks run but fail →workflow-green-repo. - Agent stopped early, claimed false completion, or gamed a check → a guard
with a regression test →
iterate-agent-harness. - Working tree → merge-ready PR, never merges →
workflow-release-prep. - Orient in an unfamiliar codebase →
workflow-onboard(product user onboarding →enhance-onboarding). - Is a lint or ratchet rule right →
audit-doctrine; is it enforced →audit-gate-logic. - These
audit-*skills fix after reporting, not present-then-stop:audit-responsive,audit-code-quality,audit-performance,audit-security,audit-i18n,audit-bundle-size.
Rules hold always-on policy and routing; procedures stay in skills.
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.
- 23d ago Changed · -179 lines · -2,975 tokens per session 7053d22bd598
- 1mo ago Changed · +2 lines · +49 tokens per session 7cfbacb4954f
- 1mo ago First seen · 211 lines · 2,959 tokens per session scan A ab91ea89aad6
skill-workflows is a cursor rule published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 18d ago), licensed MIT. It adds 33 tokens to every session and 393 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
composer-coding-excellence
Editing source, tests, types, or build files in any language — surgical diff, match the file's language idioms, run the narrowest check.
composer-core
Always-on spine — programming-first fast path, high effort on hard code, confusion-weight asks, proof labels.
clarify-first
Infer-and-act by default — ask only on high confusion weight, after inspecting, with a decision-linked question.
composer-debugging
Failing tests, errors, flaky behavior, or a bug with no clear line — reproduce, trace the data, fix the cause, prove it with one scoped test.
composer-senior-practices
Version-pinned framework guidance from primary docs when building on unfamiliar stacks, upgrading, or reviewing architecture — load when evidence beats training data; not required for routine feature work.
cursor-tools-discipline
Cursor tool harness — what may enter a turn, which tool runs, what may leave, and when to stop. Parallel reads, schema-first MCP, no fabricated output.