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/r0x0d/linux-mcp-server/agents-mdgit clone --depth 1 https://github.com/r0x0d/linux-mcp-serverWhat 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.00471 | $0.00471 |
| Opus 5 | $0.00235 | $0.00235 |
| Sonnet 5 | $0.00094 | $0.00094 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
linux-mcp-server AGENTS.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 2d 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.
What it actually says
Linux MCP Server
Read-only MCP server for Linux system diagnostics.
Commands
uv sync # Install dependencies
uv run pytest # Run tests
uv run ruff check src tests # Lint
uv run pyright # Type check
make verify # All checks (required before commit)
Project Layout
src/linux_mcp_server/tools/- MCP tools (logs, network, processes, services, storage, system_info)src/linux_mcp_server/commands.py- Command definitionssrc/linux_mcp_server/formatters.py/parsers.py- Output formatting and parsingtests/- Mirrors src structure
Rules
Code: PEP 8, type hints required, async/await for I/O, 120 char max, prefer Pydantic over dataclasses
Testing:
- Run
make verifybefore committing - Use parameterized tests and fixtures (shared fixtures go in
conftest.py) - Use
autospec=Truewhen patching;spec=<object>with MagicMock - 100% patch coverage for new code
Security (Critical):
- All tools must be read-only with
readOnlyHint=True - Validate all input, use allowlists for file paths, sanitize shell params
Adding Tools
- Create tool in
src/linux_mcp_server/tools/using@mcp.tool(),@log_tool_call,@disallow_local_execution_in_containersdecorators - Register command in
commands.py - Write tests in
tests/tools/
See src/linux_mcp_server/tools/processes.py for reference.
Commits & PRs
Use Conventional Commits: <type>(<scope>): <subject>
Types: feat, fix, docs, test, refactor, perf, chore
PRs must be small and focused - one logical change per PR. Split large changes into incremental PRs.
Docs
Full details: docs/contributing.md | Architecture: docs/architecture.md | API: docs/api/
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.
- 2d ago First seen · 55 lines · 471 tokens per session scan A b09bb51d9826
linux-mcp-server AGENTS.md is an instructions file published in the GitHub repository r0x0d/linux-mcp-server (0 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 471 tokens to every session, about $0.0024 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
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.