What is interactive-process-mcp CLAUDE.md?

Project instructions for interactive-process-mcp, including security rules, agent guidance, issue tracking, labels, documentation, and multi-session work.

Use them when working on this project, especially when creating sessions, reading process output, using GitHub Issues, applying triage labels, or updating its documentation.

They prevent sensitive information from entering the project and set consistent rules for handling issues and interactive processes.

How UserB1ank/interactive-process-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to UserB1ank/interactive-process-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/UserB1ank/interactive-process-mcp/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/UserB1ank/interactive-process-mcp

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/userb1ank/interactive-process-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/userb1ank/interactive-process-mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/userb1ank/interactive-process-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/userb1ank/interactive-process-mcp/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/userb1ank/interactive-process-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/userb1ank/interactive-process-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 597 This file is loaded in full into every session.

When invoked 597 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00597	$0.00597
Opus 5.5	$0.00239	$0.00239
Sonnet 5.5	$0.00119	$0.00119
Haiku 4.5	$0.00060	$0.00060

Measured 2mo ago against content hash 0170c46c5be3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

interactive-process-mcp CLAUDE.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 2mo 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.

CLAUDE.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Security & Privacy

禁止在项目中出现以下敏感信息和敏感文件：

本机 hostname、本地用户名称
真实密钥、API keys、tokens、passwords
邮箱地址、手机号等个人信息
.env 文件、私钥文件（PEM、SSH key 等）
禁止出现 Co-Authored-By: Claude Opus 4.7 <[email protected]> 相关字样

Agent skills

Issue tracker

Issues are tracked in GitHub Issues via gh CLI. See docs/agents/issue-tracker.md.

Triage labels

Default vocabulary: needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. See docs/agents/triage-labels.md.

Domain docs

Single-context layout: CONTEXT.md + docs/adr/ at repo root. See docs/agents/domain.md.

Multi-session parallel work

Agents using interactive-process MCP tools must follow these rules for non-blocking, multi-session operation.

Rules

One task = one session. Start a new session per independent task via start_process. Use the name param for tracking.
Never block on reads. Always use read_output with timeout ≤ 3. A long timeout blocks the entire agent — other sessions go unserviced.
Prefer send_and_read. For send-then-read patterns, use send_and_read instead of separate send_input + read_output calls. Same timeout rule applies.
Poll in rotation. When managing N sessions, loop through all of them: read_output(timeout=1) each, act on whichever has output, repeat.
Clean up. terminate_process then delete_session when done. Never leave zombie sessions.

Multi-agent shared session

When multiple agents need to observe the same process:

Agent A: start_process(...) → session_id, default reader_id=0
Agent B: register_reader(session_id=...) → gets its own reader_id
Each agent calls read_output(session_id=..., reader_id=<theirs>) — independent cursors, no output stealing
Agent B leaves: unregister_reader(session_id=..., reader_id=...)

Anti-patterns

❌ read_output(timeout=30) — blocks 30s, other sessions starve
❌ Waiting for session A to finish before starting session B — start both, poll both
❌ Multiple agents using the same reader_id — output gets consumed, others miss it
❌ Forgetting delete_session after terminate_process — stale metadata accumulates

Read the full file on GitHub · 52 lines

Changes

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.

2mo ago First seen · 52 lines · 597 tokens per session scan A 0170c46c5be3

Subscribe to this mod's changes

interactive-process-mcp CLAUDE.md is an instructions file published in the GitHub repository UserB1ank/interactive-process-mcp (8 stars, last pushed 6mo ago), licensed MIT. It adds 597 tokens to every session, about $0.0024 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.

ai-agents go interactive mcp-server model-context-protocol pty

interactive-process-mcp CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
interactive-process-mcp CLAUDE.mdUserB1ank/interactive-process-mcp	Instructions file	8	6mo ago	MIT	A	597	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

interactive-process-mcp: Instructions file for Claude Code