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/andreagriffiths11/machine-mcp/agents-mdgit clone --depth 1 https://github.com/AndreaGriffiths11/machine-mcpWrote 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/andreagriffiths11/machine-mcp/agents-md)<a href="https://agentmods.dev/instructions/andreagriffiths11/machine-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/andreagriffiths11/machine-mcp/agents-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.00531 | $0.00531 |
| Opus 5 | $0.00266 | $0.00266 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
machine-mcp 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 4d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent notes for machine-mcp
You are using the human's laptop through this MCP server. stdio means you are already inside their process. Do not invent a pairing step. Do not ask them to log into GitHub, Copilot, or Cursor through these tools.
What this is
Laptop-side tools: status, run, record_terminal, write_file, read_file. Workspace root is MACHINE_MCP_WORKSPACE or ~/machine-mcp-workspace. File tools cannot leave that root.
This does not replace Grok Bot Computers or Local execution. Those are a different control path. This server is the tool process on the machine they already use.
How to use the tools
- Call status first. Note OS, cwd, workspace, and whether copilot, ffmpeg, and git are on PATH.
- Put demo scripts and output files in the workspace with write_file / read_file. Relative paths only.
- Use run for commands that should execute in the workspace (copilot, git, ffmpeg, compilers). Pass a real argv string. Timeouts cap at 120 seconds.
- record_terminal will not produce a video. On Linux, install ffmpeg if needed and run its suggested command yourself via run. Other platforms return an unsupported-platform error. Do not fake a recording.
Never
- Never read SSH keys, Copilot config dirs, .env files, credential files, cookies, or token stores.
- Never run copilot login, gh auth login, or any login/device-code flow. Copilot CLI on this machine is already signed in. Use it.
- Never print, log, or echo secrets. run redacts github_pat_ and AWS key shapes if they leak into stdout. Do not try to bypass that.
- Never pass parent-directory segments or absolute paths to write_file / read_file.
- Never start an HTTP listener or bind a port. v1 is stdio only.
- Never git push or force-push unless the human explicitly asked in this turn.
Copilot CLI demos
Record or script Copilot CLI demos on this machine because it is already signed in. Prefer run with copilot on PATH. Keep demo artifacts inside the workspace. If you need a screen capture, use the ffmpeg command from record_terminal on Linux. Do not pretend a file exists if you did not capture one.
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.
- 4d ago First seen · 34 lines · 531 tokens per session scan A 5398b3c3f89a
machine-mcp AGENTS.md is an instructions file published in the GitHub repository AndreaGriffiths11/machine-mcp (2 stars, last pushed 6d ago), licensed MIT. It adds 531 tokens to every session, about $0.0027 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.
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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.