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/FeatureFactory-io/mimirWrote 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/featurefactory-io/mimir/do-no-shortcuts)<a href="https://agentmods.dev/rules/featurefactory-io/mimir/do-no-shortcuts"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/do-no-shortcuts/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/featurefactory-io/mimir/do-no-shortcuts"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/do-no-shortcuts.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.00350 | $0.00350 |
| Opus 5.5 | $0.00140 | $0.00140 |
| Sonnet 5.5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
do-no-shortcuts 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
Rule: No Shortcuts
Every time you are about to take a shortcut — STOP. Do it properly.
A shortcut is any path that skips the documented, release-grade, or user-approved process because something is blocked, slow, or inconvenient.
Before acting, ask
- What is the proper process for this task (SAO, playbook, pipeline, spec)?
- Am I choosing a faster path only because the proper path failed or is hard?
- If yes → do not shortcut. Fix the blocker or escalate; do not bypass.
Examples (Mimir)
| Shortcut (forbidden) | Proper path |
|---|---|
workflow_dispatch deploy + promote to prod |
gh release create vX.Y.Z → release CI → promote.yml with tag |
Promote main-<sha> revision to prod |
Promote only semver release tags (v0.0.73) |
make swap / make idle-start as primary ship |
GitHub Actions: Build and Deploy → Promote to Production |
| Ship without release because CI is broken | Fix pipeline/infra first; then release |
| Weaken tests or skip gates to go green | Fix implementation or fix tests to match spec |
When blocked
- Diagnose and fix the root cause of the proper path failing.
- Tell the user what is blocked and what the proper next step is.
- Do not substitute an alternate path without explicit user approval.
No exceptions for urgency, prior failures, or "just this once."
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 · 35 lines · 350 tokens per session scan A a3be093ee706
do-no-shortcuts is a cursor rule published in the GitHub repository FeatureFactory-io/mimir (16 stars, last pushed 17d ago), licensed Apache-2.0. It adds 350 tokens to every session, about $0.0014 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-09-16.
Other cursor rules, from other repositories
vios-testing-cicd
Testing and CI/CD conventions for VIOS.
workflow
BDD-style workflow, UI screenshots in the PR, HTTP OpenAPI, config schema and CLI packaging sync before lint, final checks, the comment on an issue a merge closes and the cleanup after the merge.
build-tags
The shipped build tag set is spelled in several places that move together.
add-linter
Add linter configs and GitHub Actions workflows for languages detected in the current repo. Use when the user wants to add linters, set up code quality checks, or after sync-scaffold suggests running /add-linter.
testing-ci-rule
testing-ci-rule from DaunteEth/woofi-pro-mcp.
435-ci-cd-testing-gatekeeper
Purpose: Enforce quality and reliability via CI/CD.