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.
npx agentmods add instructions/waylaidwanderer/background-process-mcp/gemini-mdgit clone --depth 1 https://github.com/waylaidwanderer/background-process-mcpWrote 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/instructions/waylaidwanderer/background-process-mcp/gemini-md)<a href="https://agentmods.dev/instructions/waylaidwanderer/background-process-mcp/gemini-md"><img src="https://agentmods.dev/badge/instructions/waylaidwanderer/background-process-mcp/gemini-md.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.00512 | $0.00512 |
| Opus 5 | $0.00256 | $0.00256 |
| Sonnet 5 | $0.00102 | $0.00102 |
| Haiku 4.5 | $0.00051 | $0.00051 |
Grade A, and why
background-process-mcp GEMINI.md 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 6d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Background Process Manager Extension
This extension provides a robust set of tools for managing background processes. It is your primary interface for any long-running or interactive tasks.
Usage Strategy
Core Principles
-
Long-Running & Interactive Processes: You MUST use
start_processfor any command that does not exit immediately or may require user input. This is non-negotiable.- Examples:
npm run dev,vite,tsc --watch, servers, or any kind of file watcher.
- Examples:
-
Short-Lived Commands (The Exception): For short-lived, synchronous commands (e.g.,
ls,cat,pnpm test,pnpm build), you should ALWAYS prefer your native shell tool (e.g.,run_shell_command).- Only use
run_command_syncas a fallback if the native tool is failing, or for specific, niche reasons where running the command through this MCP provides a clear advantage.
- Only use
Available Tools
start_process: Starts a new process in the background. This is the required tool for all long-running commands (servers, watchers) or interactive tasks.command(string): The command to run.
stop_process: Stops a running background process.processId(string): The UUID of the process to stop.
clear_process: Clears a stopped background process from the list.processId(string): The UUID of the process to clear.
get_process_output: Gets the recent output for a background process. Can specifyheadortail.processId(string): The UUID of the process.head(number, optional): Get the first N lines of output.tail(number, optional): Get the last N lines of output.
get_server_status: Gets the current status of the Background Process Manager server.list_processes: Gets a list of all processes being managed by the Background Process Manager.run_command_sync: Runs a short-lived command and waits for it to complete. You should prefer your native shell tools for this. Use this tool only when there is a specific need to run a synchronous command within the context of this MCP.command(string): The command to run.
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.
- 6d ago First seen · 33 lines · 512 tokens per session scan A ddd2817c878c
background-process-mcp GEMINI.md is an instructions file published in the GitHub repository waylaidwanderer/background-process-mcp (11 stars, last pushed 10mo ago), licensed MIT. It adds 512 tokens to every session, about $0.0026 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-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.