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/chenchihcu/devspace-mcp/agents-mdgit clone --depth 1 https://github.com/chenchihcu/DevSpace-MCPWhat 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.00351 | $0.00351 |
| Opus 5 | $0.00176 | $0.00176 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
DevSpace-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 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
100% identical to devspace-local-artifacts AGENTS.md — 0 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.
What it actually says
DevSpace
This project exposes a local development workspace over MCP so ChatGPT, Claude, or another MCP-capable host can operate directly on this machine's approved development directories.
The goal is not to delegate work to a separate local coding agent. The MCP host should call tools that read files, edit files, search code, and run shell commands directly against approved local project roots.
Pi's SDK is currently used as the backend adapter for mature local coding primitives such as read, edit, write, grep, find, ls, and bash. DevSpace wraps those primitives behind a remote Streamable HTTP MCP interface, suitable for use through a Cloudflare Tunnel.
The model-facing workflow is workspace based. MCP clients should call
open_workspace once per local project directory or worktree, then reuse the
returned workspaceId for subsequent tool calls in that same folder. Do not
call open_workspace again for the same folder unless the workspaceId is
rejected as unknown, the client switches folders/worktrees or checkout/worktree
mode, or the user explicitly asks to reopen. AGENTS.md files are returned
automatically by open_workspace and by later tool calls when the requested path
enters a directory with instructions that have not been loaded for that
workspace.
Core constraints:
- Treat this as remote access to the local machine; security is part of the core design, not a later add-on.
- Start with a narrow filesystem allowlist.
- Prefer explicit, inspectable tool calls over autonomous local agent loops.
- Keep the first version small enough to validate with real ChatGPT/Claude MCP clients before adding UI or workflow features.
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 · 34 lines · 351 tokens per session scan A 0685189d429d
DevSpace-MCP AGENTS.md is an instructions file published in the GitHub repository chenchihcu/DevSpace-MCP (0 stars, last pushed 2mo ago), licensed MIT. It adds 351 tokens to every session, about $0.0018 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to devspace-local-artifacts AGENTS.md, differing in 0 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.
buildNext
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
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
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.