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.
npx agentmods add rules/vypdev/copilot/usecase-flowsgit clone --depth 1 https://github.com/vypdev/copilotWhat 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 | $0.00017 | $0.01630 |
| Opus 5 | $0.00009 | $0.00815 |
| Sonnet 5 | $0.00003 | $0.00326 |
| Haiku 4.5 | $0.00002 | $0.00163 |
Grade A, and why
usecase-flows 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use case flows (schematic)
Entry point: mainRun(execution) in src/actions/common_action.ts. After execution.setup() and optionally waitForPreviousRuns, the dispatch is:
mainRun
├── runnedByToken && singleAction → SingleActionUseCase (only if validSingleAction)
├── issueNumber === -1 → SingleActionUseCase (only if isSingleActionWithoutIssue) or skip
├── welcome → log boxen and continue
└── try:
├── isSingleAction → SingleActionUseCase
├── isIssue → issue.isIssueComment ? IssueCommentUseCase : IssueUseCase
├── isPullRequest → pullRequest.isPullRequestReviewComment ? PullRequestReviewCommentUseCase : PullRequestUseCase
├── isPush → CommitUseCase
└── else → core.setFailed
1. IssueUseCase (on: issues, not a comment)
Step order:
- CheckPermissionsUseCase → if it fails (not allowed): CloseNotAllowedIssueUseCase and return.
- RemoveIssueBranchesUseCase (only if
cleanIssueBranches). - AssignMemberToIssueUseCase
- UpdateTitleUseCase
- UpdateIssueTypeUseCase
- LinkIssueProjectUseCase
- CheckPriorityIssueSizeUseCase
- PrepareBranchesUseCase (if
isBranched) or RemoveIssueBranchesUseCase (if not). - RemoveNotNeededBranchesUseCase
- DeployAddedUseCase (deploy label)
- DeployedAddedUseCase (deployed label)
- If issue.opened:
- If not release and not question/help → RecommendStepsUseCase
- If question or help → AnswerIssueHelpUseCase
2. IssueCommentUseCase (on: issue_comment)
Step order:
- CheckIssueCommentLanguageUseCase (translation)
- DetectBugbotFixIntentUseCase → payload:
isFixRequest,isDoRequest,targetFindingIds,context,branchOverride - ProjectRepository.isActorAllowedToModifyFiles(owner, actor, token) (permission to modify files)
- Branch A – if runAutofix && allowed:
- BugbotAutofixUseCase → runBugbotAutofixCommitAndPush → if committed: markFindingsResolved
- Branch B – if !runAutofix && canRunDoUserRequest && allowed:
- DoUserRequestUseCase → runUserRequestCommitAndPush
- If no file-modifying action ran → ThinkUseCase
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.
- yesterday First seen · 149 lines · 17 tokens per session scan A e546d0ecebfc
usecase-flows is a cursor rule published in the GitHub repository vypdev/copilot (2 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 1,630 once invoked, about $0.0001 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.
Other cursor rules, from other repositories
code-review-en
Code Review Guidelines (English).
code-review
代码审查规范(中文版).
cursorrules
See AGENTS.md — Cursor reads it natively.
task-summary
Enforce Summary and Session Log blocks on every coding response when session tracking is enabled.
api-steps
How to create HTTP endpoints in Motia.
virtual-steps
Connecting nodes virtually and creating a smooth flow in Workbench.