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/vypdev/copilotWrote 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/vypdev/copilot/usecase-flows)<a href="https://agentmods.dev/rules/vypdev/copilot/usecase-flows"><img src="https://agentmods.dev/badge/rules/vypdev/copilot/usecase-flows/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/vypdev/copilot/usecase-flows"><img src="https://agentmods.dev/badge/rules/vypdev/copilot/usecase-flows.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.00008 | $0.00217 |
| Opus 5.5 | $0.00003 | $0.00087 |
| Sonnet 5.5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
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 1mo 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
Use case flows
The maintained flow catalog is _agent/docs/usecase-flows.md. Read that file
and the current composition roots before changing orchestration; this rule does
not carry a second action list that can drift.
At a high level:
GitHub/local input
-> setup and workflow queue
-> resolveMainRunRoute
-> composed issue, PR, push, comment, or single-action handler
-> application workflows behind semantic ports
Release and hotfix operations enter through the canonical durable callbacks:
prepare_deployment_action, continue_deployment_action,
published_deployment_action, and failed_deployment_action. Their exact
catalog lives only in src/data/model/action_types.ts.
Issue workflow labels may prepare a release or hotfix branch, but publication,
promotion, reconciliation, and cleanup belong to
DeploymentOrchestrationUseCase. Do not introduce a label-driven completion or
a second PR merge path.
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.
- 1mo ago Changed · -118 lines · -9 tokens per session 9aef862247b7
- 1mo ago Changed ae845afed038
- 1mo ago First seen · 149 lines · 17 tokens per session scan A e546d0ecebfc
usecase-flows is a cursor rule published in the GitHub repository vypdev/copilot (3 stars, last pushed today), licensed MIT. It adds 8 tokens to every session and 217 once invoked, about $0.0000 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
code-review-en
Code Review Guidelines (English).
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.
201-bugbot-autofix
200: Responding to BugBot PR comments.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.