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/sarks0/mcp-shellgateway/claude-mdgit clone --depth 1 https://github.com/Sarks0/mcp-ShellGatewayWrote 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/sarks0/mcp-shellgateway/claude-md)<a href="https://agentmods.dev/instructions/sarks0/mcp-shellgateway/claude-md"><img src="https://agentmods.dev/badge/instructions/sarks0/mcp-shellgateway/claude-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 | $0.01029 | $0.01029 |
| Opus 5 | $0.00515 | $0.00515 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
mcp-ShellGateway 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 3d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Common Development Commands
Testing
# Run all tests
python -m pytest tests/
# Run tests with coverage
python -m pytest tests/ --cov=linux_shell_server --cov-report=html
# Run specific test file
python -m pytest tests/test_main.py -v
Code Quality
# Format code
black linux_shell_server/ tests/
# Check code style
ruff check linux_shell_server/ tests/
# Sort imports
isort linux_shell_server/ tests/
# Type checking
mypy linux_shell_server/
Running the Server
# Test server directly
python -m linux_shell_server.main
Architecture Overview
This is an MCP (Model Context Protocol) server that provides Linux shell command execution capabilities to Claude Desktop.
Core Components
ShellExecutor (linux_shell_server/main.py:68-293):
- Manages command execution with async subprocess calls
- Handles timeouts (30s default, 120s for long commands)
- Maintains working directory state
- Implements command result caching for performance
- Truncates output at 10KB to prevent memory issues
MCP Protocol Implementation (linux_shell_server/main.py:297-428):
- Three tools:
execute_command,change_directory,get_current_directory - Implements required MCP endpoints:
list_tools,list_resources,list_prompts,call_tool - Uses stdio for communication with Claude Desktop
Key Design Patterns
- Process Management: Creates process groups for proper cleanup on timeout
- Error Handling: All operations return structured error responses
- Path Validation: Directory changes are validated before execution
- Async Architecture: Built on asyncio for non-blocking operations
Testing Approach
Tests in tests/test_main.py cover:
- Command execution success/failure cases
- Directory operations and validation
- MCP protocol handler responses
- Edge cases (empty commands, invalid paths, timeouts)
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.
- 3d ago First seen · 131 lines · 1,029 tokens per session scan A 66c2ab7362cf
mcp-ShellGateway CLAUDE.md is an instructions file published in the GitHub repository Sarks0/mcp-ShellGateway (3 stars, last pushed 1y ago), licensed MIT. It adds 1,029 tokens to every session, about $0.0051 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-31.
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).
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.
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.