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/alkindivv/mcpishcode/agents-mdgit clone --depth 1 https://github.com/alkindivv/MCPishCodeWhat 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.01640 | $0.01640 |
| Opus 5 | $0.00820 | $0.00820 |
| Sonnet 5 | $0.00328 | $0.00328 |
| Haiku 4.5 | $0.00164 | $0.00164 |
Grade A, and why
MCPishCode 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 yesterday.
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.
This is a copy
92% identical to devspace AGENTS.md — 25 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCPishCode
MCPishCode is a local development execution layer for MCP hosts such as ChatGPT and Claude. It gives a remote host workspace-scoped tools for reading, editing, searching, running commands, managing Git worktrees, reviewing changes, and coordinating bounded subagents on the user's machine.
Pi's SDK currently provides mature local coding primitives. MCPishCode wraps those primitives in a Streamable HTTP MCP server and adds the product-specific boundaries around them: approved roots, workspace state, instructions, process sessions, worktrees, artifacts, review checkpoints, widgets, and subagent execution.
Product model
These ideas should stay true as the project evolves:
- The host is the orchestrator. MCPishCode exposes clear capabilities and execution state. It should not hide the workflow inside an opaque, uninspectable agent loop.
- Everything happens in a workspace. A workspace represents one local project directory or worktree plus the instructions and state accumulated while operating in it.
- Local authority stays explicit. MCPishCode runs with access to the user's machine. Roots, paths, commands, processes, credentials, and destructive operations must be treated as product boundaries.
- Subagents are bounded workers. A subagent should have an explicit task, profile, working context, lifecycle, and result that the host can inspect and coordinate.
- Adapters stay at the edges. Pi, MCP hosts, and model providers each have their own terminology and capabilities. Provider-specific behavior should not become the core domain model.
- Prefer composable primitives. Build a small set of reliable operations that can be combined into larger workflows instead of baking every workflow into the server.
Glossary
- Host — the MCP client presenting the agent experience and coordinating work.
- Server — the local MCPishCode MCP server.
- Workspace — one opened directory or worktree and its accumulated instruction context.
workspaceId— the opaque handle returned byopen_workspaceand reused for calls in that workspace.- Allowed root — a configured filesystem boundary within which a workspace may be opened. It is not itself necessarily a workspace.
- Checkout mode — operating on an existing checkout supplied by the user.
- Worktree mode — operating in an isolated Git worktree.
- Tool surface — the tools exposed by a configured mode, such as minimal, full, or Codex-compatible.
- Process session — a long-running command tracked for later input, output, or termination.
- Instruction file — an
AGENTS.mdorCLAUDE.mddiscovered while navigating a workspace. - Subagent — a bounded model invocation delegated and coordinated by the host.
- Agent profile — the model, provider, tools, and instructions used for a subagent.
- Artifact — an output surfaced for the host or user to inspect.
- Review checkpoint — stored state representing a coherent set of changes.
- Widget — host-rendered UI/Cards attached to an MCP response.
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.
- yesterday First seen · 117 lines · 1,640 tokens per session scan A f5bdc54610e7
MCPishCode AGENTS.md is an instructions file published in the GitHub repository alkindivv/MCPishCode (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,640 tokens to every session, about $0.0082 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to devspace AGENTS.md, differing in 25 lines, and is treated as a copy.
Other instructions, from other repositories
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 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).
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.
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).
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.
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.