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/wei6bin/skillsWrote 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/wei6bin/skills/jidoka-cursor)<a href="https://agentmods.dev/rules/wei6bin/skills/jidoka-cursor"><img src="https://agentmods.dev/badge/rules/wei6bin/skills/jidoka-cursor/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/wei6bin/skills/jidoka-cursor"><img src="https://agentmods.dev/badge/rules/wei6bin/skills/jidoka-cursor.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.01150 | $0.01150 |
| Opus 5.5 | $0.00460 | $0.00460 |
| Sonnet 5.5 | $0.00230 | $0.00230 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
jidoka-cursor 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 10d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jidoka on Cursor
This plugin (jidoka-cursor) is the Cursor render of jidoka: its skills and agents already
use Cursor's subagent_type and model slugs. Use this rule whenever running the line skill
or implementing from docs/new-feature/*/04-task-plan.md.
Dispatch (Task tool)
Use subagent_type with the bare agent name - never agent_type, never a jidoka: prefix.
| Phase | subagent_type |
Notes |
|---|---|---|
| 1 - project setup | project-scaffolder |
Only when the project-setup skill runs (no source code in the folder, or a request for a new project), after its one batched question: one task with the repo root, the Git answer, the skeleton contract and the chosen stack rows. The scaffolder itself dispatches impl-backend and impl-frontend (scope "project scaffold - {backend|frontend} - skill: {scaffold skill} - root: {dir}"), or builds both halves itself if Cursor refuses a nested task |
| 2 - exploration | code-explorer |
2-3 parallel tasks, different angles |
| 4 - architecture | code-architect |
One task with Phase 2-3 context |
| 6 - plan review | plan-reviewer |
Two parallel tasks (AC/security vs tasks/tests) |
| 8 - backend half | impl-backend |
Scope e.g. "SLICE-01 backend half"; dispatched concurrently with the frontend half against the slice's frozen Contract:. Append the lean mode from the slice's story-point size - lean: lite (1-2 pts) / lean: full (3+, default). Large slices (8+/spike) stay full - the implementer flags over-scope, never drops an AC |
| 8 - frontend half | impl-frontend |
Dispatched concurrently with the backend half (single batch), scope "SLICE-01 frontend half - build against the frozen contract with a typed mock; do not wait for the backend; stay on the mock, no per-slice integration"; append the same lean: token. One "whole-story integration" re-dispatch at the end (after every slice lands) swaps every slice's mock for the real backends and reconciles drift across the story |
| 8 - simplify | impl-simplify |
Once, over the whole-story diff (folder, branch-point ref, changed-file list), before review |
| 8 - review | code-reviewer, security-reviewer |
One parallel batch over the whole-story diff after simplify; refactor tier dispatches code-reviewer only |
| 9 - walkthrough | test-plan-walker |
Clean context; do not inline Phase 9 in parent |
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.
- 10d ago Changed · +1 lines · +124 tokens per session a2b3dcd09c8b
- 17d ago First seen · 63 lines · 1,026 tokens per session scan A 7b804730acc0
jidoka-cursor is a cursor rule published in the GitHub repository wei6bin/skills (2 stars, last pushed 11d ago), licensed MIT. It adds 1,150 tokens to every session, about $0.0046 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-10-02.
Other cursor rules, from other repositories
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
shared-plane-packages
Pattern for creating shared plane packages that serve both migration and runtime planes.