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/localrivet/gomcpWrote 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/localrivet/gomcp/no-background-processes)<a href="https://agentmods.dev/rules/localrivet/gomcp/no-background-processes"><img src="https://agentmods.dev/badge/rules/localrivet/gomcp/no-background-processes/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/localrivet/gomcp/no-background-processes"><img src="https://agentmods.dev/badge/rules/localrivet/gomcp/no-background-processes.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.00474 | $0.00474 |
| Opus 5.5 | $0.00190 | $0.00190 |
| Sonnet 5.5 | $0.00095 | $0.00095 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
no-background-processes 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
No Background Processes Rule
CRITICAL: Never run any programs, servers, or processes in the background
Strict Prohibitions
- ❌ NEVER use
&to run commands in background - ❌ NEVER use
nohupor similar background process tools - ❌ NEVER set
is_background: truein terminal commands - ❌ NEVER run servers, applications, or long-running processes in background
- ❌ NEVER use
screen,tmux, or detached sessions
Why This Rule Exists
- Debugging Difficulty: Background processes make it impossible to see real-time output and errors
- Process Management: Background processes can become orphaned and difficult to stop
- User Control: Users need to see what's happening and control when processes start/stop
- Resource Management: Hidden background processes consume system resources unknowingly
Correct Approaches
- ✅ Run processes in foreground so output is visible
- ✅ Use
Ctrl+Cto stop processes when needed - ✅ Ask user before starting any long-running process
- ✅ Explain what will happen before running commands
- ✅ Use short-lived commands when possible
Examples
# ❌ WRONG - Background process
go run main.go &
npm run dev &
# ✅ CORRECT - Foreground process
go run main.go
npm run dev
# ❌ WRONG - Background with timeout
timeout 10 go run main.go &
# ✅ CORRECT - Ask user to run manually
echo "Please run 'go run main.go' in a separate terminal"
When Long-Running Processes Are Needed
- Ask the user to run the command in a separate terminal
- Provide clear instructions on what command to run
- Explain why the process needs to run
- Give guidance on how to stop it when done
Emergency Exception
The ONLY exception is if the user explicitly requests a background process and understands the implications. Even then, prefer asking them to run it manually.
This rule has NO exceptions for convenience - user visibility and control always takes priority.
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 · 63 lines · 474 tokens per session scan A bf91fef65499
no-background-processes is a cursor rule published in the GitHub repository localrivet/gomcp (51 stars, last pushed 1y ago), licensed MIT. It adds 474 tokens to every session, about $0.0019 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-30.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.