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/nightnei/wordpress-developer-mcp-server/agents-mdgit clone --depth 1 https://github.com/nightnei/wordpress-developer-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.01164 | $0.01164 |
| Opus 5 | $0.00582 | $0.00582 |
| Sonnet 5 | $0.00233 | $0.00233 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
wordpress-developer-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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WordPress Developer MCP Server
Project Overview
This repository builds and ships a standalone MCP server that lets AI assistants manage local WordPress sites. The TypeScript source lives in src/, the bundled release entrypoint is dist/index.cjs, and the macOS/Windows installers wire the bundled server into supported AI apps.
Release artifacts contain only the bundled server file from dist/, so changes to src/ must be followed by npm run build.
Common Commands
- Install dependencies:
npm ci - Build release bundle:
npm run build - Typecheck:
npm run typecheck - Inspect MCP server locally:
npm run inspect - Shell syntax checks:
bash -n install.shandbash -n uninstall.sh
If PowerShell is available, parse-check the Windows scripts after editing them:
$errors = $null
$null = [System.Management.Automation.Language.Parser]::ParseFile("install.ps1", [ref]$null, [ref]$errors)
if ($errors.Count) { $errors | ForEach-Object { Write-Error $_ }; exit 1 }
$null = [System.Management.Automation.Language.Parser]::ParseFile("uninstall.ps1", [ref]$null, [ref]$errors)
if ($errors.Count) { $errors | ForEach-Object { Write-Error $_ }; exit 1 }
Code Style
- Use TypeScript ESM imports and keep
stricttypechecking clean. - Match the existing formatting: tabs for indentation, single quotes, semicolons.
- Keep comments short and only where they explain non-obvious platform behavior or workarounds.
- Prefer existing helper patterns over new abstractions.
- Keep installer changes conservative; they run on user machines and should be easy to audit.
Architecture Notes
src/index.tscreates the MCP server and concatenates always-on server instructions.src/tools/contains tool registrations grouped by feature area.src/lib/studio-cli.tsowns Studio CLI process execution. Windows.cmdbehavior is delicate; do not simplify it without retesting Windows.src/lib/node-runtime.tsowns lookup for commands provided by the Node runtime. Installed MCP uses the bundled Node/npm under~/.wordpress-developer-mcp/node; runtime code that needs npm or Node-provided commands must resolve them through this helper instead of assuming globalnode,npm, ornpm.cmdare on PATH.src/lib/package.tsderives MCPserverInfo.versionfrompackage.json.install.shis macOS-focused.install.ps1is Windows-focused and also supports the programmatic-Updatepath used by the MCP update tool.- Update mode should refresh runtime/server/wrappers only; avoid auth prompts or app configuration during programmatic updates.
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 · 125 lines · 1,164 tokens per session scan A 0998da7d9ad2
wordpress-developer-mcp-server AGENTS.md is an instructions file published in the GitHub repository nightnei/wordpress-developer-mcp-server (65 stars, last pushed 2mo ago), licensed MIT. It adds 1,164 tokens to every session, about $0.0058 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-30.
Other instructions, from other repositories
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.
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).
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.