unix-mcp-server: Instructions file for Codex

AGENTS.md

unix-mcp-server AGENTS.md is an instructions file for Codex, OpenCode from ahmedadan/unix-mcp-server. It costs 520 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for a read-only MCP server that reports Unix-like system information, including logs, networks, processes, services, storage, and general system details.

In plain words
What is it for?
Use them when adding or changing system-diagnostic tools, running project checks, or testing parsers and output formatting.
Why use it?
They set the testing, typing, validation, and security rules needed to keep diagnostic tools read-only and safe.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is ahmedadan/unix-mcp-server's own configuration. It tells Codex and OpenCode how to work on unix-mcp-server 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 unix-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ahmedadan/unix-mcp-server. 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/ahmedadan/unix-mcp-server/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/ahmedadan/unix-mcp-server

Made for: Codex, OpenCode.

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 unix-mcp-server AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ahmedadan/unix-mcp-server/agents-md.svg)](https://agentmods.dev/instructions/ahmedadan/unix-mcp-server/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/ahmedadan/unix-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/ahmedadan/unix-mcp-server/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 520 This file is loaded in full into every session.
When invoked 520 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00520 $0.00520
Opus 5 $0.00260 $0.00260
Sonnet 5 $0.00104 $0.00104
Haiku 4.5 $0.00052 $0.00052

Measured 7d ago against content hash da298e1eb3cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

unix-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 7d 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.

AGENTS.md · 58 lines

How it starts

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

Unix MCP Server

Read-only MCP server for Unix-like 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/unix_mcp_server/tools/ - MCP tools (logs, network, processes, services, storage, system_info)
  • src/unix_mcp_server/commands.py - Command definitions
  • src/unix_mcp_server/formatters.py / parsers.py - Output formatting and parsing
  • tests/ - 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 verify before committing
  • Use parameterized tests and fixtures (shared fixtures go in conftest.py)
  • Use pytest-mock (mocker fixture) for mocking instead of unittest.mock imports
  • Use autospec=True when patching; spec=<object> with Mock
  • 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

  1. Create tool in src/unix_mcp_server/tools/ using @mcp.tool(), @log_tool_call, @disallow_local_execution_in_containers decorators
  2. Register command in commands.py
  3. Write tests in tests/tools/

See src/unix_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

Tool docs under docs/tools/ are auto-generated — run uv run python scripts/generate_tool_docs.py after adding or modifying tools.

Read the full file on GitHub · 58 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.

  1. 7d ago First seen · 58 lines · 520 tokens per session scan A da298e1eb3cc

Subscribe to this mod's changes

unix-mcp-server AGENTS.md is an instructions file published in the GitHub repository ahmedadan/unix-mcp-server (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 520 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-09-01.

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,153 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