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/hlalljie/agent-workflow-presetsWrote 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/hlalljie/agent-workflow-presets/check-shared-before-scoped)<a href="https://agentmods.dev/rules/hlalljie/agent-workflow-presets/check-shared-before-scoped"><img src="https://agentmods.dev/badge/rules/hlalljie/agent-workflow-presets/check-shared-before-scoped.svg" alt="Measured on agentmods" 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.00111 | $0.00111 |
| Opus 5 | $0.00056 | $0.00056 |
| Sonnet 5 | $0.00022 | $0.00022 |
| Haiku 4.5 | $0.00011 | $0.00011 |
Grade A, and why
check-shared-before-scoped 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 7d 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
Before writing a scoped override (targeting a specific component, ID, or section), check if a shared class, function, or component already handles that behavior.
If yes — ask: "This looks like it's handled by [shared thing] for all [types] — should the change apply everywhere or just here?"
Applies to CSS overrides, component-specific logic that mirrors shared logic, and markup added to one variant that others don't have.
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.
- 7d ago First seen · 11 lines · 111 tokens per session scan A 1fa36876bf43
check-shared-before-scoped is a cursor rule published in the GitHub repository hlalljie/agent-workflow-presets (2 stars, last pushed 2mo ago), licensed MIT. It adds 111 tokens to every session, about $0.0006 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
learn-as-you-build
Learn As You Build — name concepts and teach reasoning during every session.
architect
Winston — System Architect agent.
code-reviewer
Riley Stone — Code Reviewer agent.
orchestrator
Atlas Prime — Orchestrator agent.
game-architect
Game Architect agent (Cloud Dragonborn).
game-dev-scrum-master
Game Dev Scrum Master agent (Max).