mcp-console-automation: Instructions file for Claude Code

CLAUDE.md

mcp-console-automation CLAUDE.md is an instructions file for Claude Code from ooples/mcp-console-automation. It costs 397 tokens per session, scanned A, original, MIT.

Project-specific instructions for developing Console Automation MCP, a tool for managing terminal sessions over SSH, which lets you operate remote computers from a command-line connection.

In plain words
What is it for?
Use it when changing the ooples/mcp-console-automation project, especially its code organization, fixes, enhancements, and validation process.
Why use it?
It prevents duplicate implementations and sets required checks, such as linting, type checking, and testing, before changes are considered complete.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is ooples/mcp-console-automation's own configuration. It tells Claude Code how to work on mcp-console-automation itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything mcp-console-automation configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ooples/mcp-console-automation. 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/ooples/mcp-console-automation/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/ooples/mcp-console-automation

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.

agentmods badge for mcp-console-automation CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ooples/mcp-console-automation/claude-md.svg)](https://agentmods.dev/instructions/ooples/mcp-console-automation/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/ooples/mcp-console-automation/claude-md"><img src="https://agentmods.dev/badge/instructions/ooples/mcp-console-automation/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 397 This file is loaded in full into every session.
When invoked 397 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00397 $0.00397
Opus 5 $0.00198 $0.00198
Sonnet 5 $0.00079 $0.00079
Haiku 4.5 $0.00040 $0.00040

Measured 6d ago against content hash 8ec30434e5ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

mcp-console-automation 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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

CLAUDE.md · 46 lines

What it actually says

Claude Development Guidelines

Project Information

Important Rules

Code Organization and Improvements

  1. NO SEPARATE "IMPROVED" VERSIONS: When making enhancements or fixes:

    • Always modify the original file or class directly
    • Do NOT create separate "Improved", "Enhanced", "Fixed" or similar versions
    • Maintain a single source of truth for each component
    • If significant changes are needed, refactor the existing code instead of duplicating
  2. Version Management:

    • Use version control (git) for tracking changes, not file duplication
    • Keep the codebase clean and maintainable with single implementations
    • Document major changes in comments or commit messages, not separate files
  3. Testing and Validation:

    • Always run lint and typecheck commands after making changes
    • Test changes thoroughly before considering work complete
    • Run: npm run lint and npm run typecheck (or equivalent commands)

Project-Specific Guidelines

Console Automation MCP (ooples/mcp-console-automation)

  • This project handles console session management with comprehensive diagnostics
  • Canonical repository: https://github.com/ooples/mcp-console-automation
  • Previous package name was mcp-console-automation (maintained for backward compatibility)
  • Key components:
    • ConsoleManager: Core session management
    • DiagnosticsManager: Diagnostic tracking and reporting
    • SessionValidator: Session health validation

Session Management Best Practices

  • Properly handle both one-shot and persistent sessions
  • Validate session state before operations
  • Clean up resources and handle errors gracefully
  • Track session lifecycle events for diagnostics
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.

  1. 6d ago First seen · 46 lines · 397 tokens per session scan A 8ec30434e5ee

Subscribe to this mod's changes

mcp-console-automation CLAUDE.md is an instructions file published in the GitHub repository ooples/mcp-console-automation (47 stars, last pushed 3d ago), licensed MIT. It adds 397 tokens to every session, about $0.0020 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.

Related

Other instructions, from other repositories

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,182 tokens

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

microsoft/vscode · 6,785 tokens

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

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens