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/LiuYihey/Agent-EngineeringWrote 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/liuyihey/agent-engineering/request-decision-flow)<a href="https://agentmods.dev/rules/liuyihey/agent-engineering/request-decision-flow"><img src="https://agentmods.dev/badge/rules/liuyihey/agent-engineering/request-decision-flow/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/liuyihey/agent-engineering/request-decision-flow"><img src="https://agentmods.dev/badge/rules/liuyihey/agent-engineering/request-decision-flow.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.00387 | $0.00387 |
| Opus 5.5 | $0.00155 | $0.00155 |
| Sonnet 5.5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
request-decision-flow 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
Request Decision Flow
Default: follow this workflow for every user request unless it is clearly trivial or the solution is very deterministic. Do not try to judge whether a request is "complex" - when in doubt, apply this rule.
When to skip this rule
Skip only when both are true:
- Trivial problem - a single, obvious change with no meaningful trade-offs (typo fix, rename, one-line config tweak, pure explanation of existing code, "run this command").
- Very deterministic solution - exactly one correct approach; no real design choice (user already named the approach, or codebase convention leaves no alternative).
If either condition is unclear, do not skip.
Skill-first routing
Before implementation, pick the right skill:
- Requirements unclear, many constraints, or high-impact decisions -> call the
grill-meskill first and clarify with the user. - Design / exploration / discovery (architecture, new feature shape, trade-off analysis) -> call the
brainstormingskill first to widen and structure the solution space.
When unsure which skill fits, prefer grill-me for execution-bound tasks and brainstorming for open-ended design.
Multi-solution decision gate
If there are multiple valid approaches that could satisfy the requirement, call the AskQuestion tool and present clear options before implementation.
- Put the recommended option first and mark it as recommended.
- Do not bypass this step unless the user has already explicitly chosen an approach.
Scope control
- Keep options focused on the same user goal; do not expand into unrelated refactors.
- After user selection, execute decisively on the chosen 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 First seen · 39 lines · 387 tokens per session scan A a08248b5a10c
request-decision-flow is a cursor rule published in the GitHub repository LiuYihey/Agent-Engineering (5 stars, last pushed 2mo ago), licensed MIT. It adds 387 tokens to every session, about $0.0015 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
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.