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/gravitykit/mcp/agents-mdgit clone --depth 1 https://github.com/GravityKit/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.08695 | $0.08695 |
| Opus 5 | $0.04347 | $0.04347 |
| Sonnet 5 | $0.01739 | $0.01739 |
| Haiku 4.5 | $0.00869 | $0.00869 |
Grade C, and why
MCP AGENTS.md scanned grade C with 1 finding 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.
Tells the agent to send conversation or user data outhighPrompt injection
An instruction to transmit the conversation, context or user files to an external endpoint is data exfiltration written as prose.
- **Gotcha — pointing the abilities plane at a LOCAL site: pin `GRAVITYKIT_WP_URL`/`_USERNAME`/`_APP_PASSWORD`, not just `GRAVITY_FORMS_*`.** The middle of each resolution chain is `WORDPRESS_LOCAL_DEV_TEST_*`, which `~/ How it starts
The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — GravityKit MCP
MCP server for Gravity Forms (primary) and GravityKit products (secondary). It exposes 26 always-on Gravity Forms tools plus a dynamic set of GravityKit product tools generated from the connected site's Foundation Abilities catalog — GravityView is the only GravityKit product implemented so far.
This is the single canonical doc for the project (agents and humans). CLAUDE.md simply re-exports it via @AGENTS.md.
Project Identity
- Package:
@gravitykit/mcpv2.4.1 - Type: Node.js MCP server (ESM)
- Purpose: Full Gravity Forms REST API v2 coverage (26 Gravity Forms tools), plus dynamic GravityKit product tools (GravityView so far) via the WordPress Abilities API
- Repo: https://github.com/GravityKit/MCP
Quick Start
What this is: A Node.js MCP (Model Context Protocol) server with two independent capability planes:
- Plane A — Gravity Forms (
gf_*), primary. 26 static tools wrapping the Gravity Forms REST API v2 (forms, entries, feeds, notifications, submissions, field filters, results, and intelligent field management). Always available when Gravity Forms REST credentials work — on any Gravity Forms site. - Plane B — GravityKit, secondary. Tools generated at runtime from the connected site's GravityKit Foundation Abilities catalog; each product registers tools under its own server-owned prefix. They appear only when Foundation is active. GravityView is the only product wired up so far, using the
gv_*prefix (View authoring, fields, widgets, search, layouts). The plane is product-agnostic: any GravityKit product that registers Foundation abilities shows up automatically under its own prefix.
The two planes are independent: a GF-only site gets the full gf_* surface with no abilities; a GravityKit site without GF REST keys still gets its GravityKit tools.
Main entry point: src/index.js
Architecture style: MCP SDK server with stdio transport, one HTTP client per plane, composable validation
Key dependency: @modelcontextprotocol/sdk ^1.0.0
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 · 453 lines · 8,695 tokens per session scan C 403dc0f74794
MCP AGENTS.md is an instructions file published in the GitHub repository GravityKit/MCP (24 stars, last pushed 1mo ago), licensed MIT. It adds 8,695 tokens to every session, about $0.0435 per session on Opus 5. A static security scan graded it C with 1 finding (tells the agent to send conversation or user data out). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
woocommerce AGENTS.md
AGENTS.md instructions for woocommerce/woocommerce, covering woocommerce monorepo - ai agents documentation, project overview, navigation guide, which documentation to use? and available skills.
woocommerce CLAUDE.md
Claude Code instructions for woocommerce/woocommerce, a project described as: A customizable, open-source ecommerce platform built on WordPress. Build any commerce solution you can imagine.
mcp-wordpress CLAUDE.md
Instructions for docdyhr/mcp-wordpress: Project instructions live in AGENTS.md (DOX hierarchical framework — read it and its Child DOX Index before editing anything). This file exists only because Claude Code looks for CLAUDE.md specifically; keep it as a pointer, not a second copy, to avoid drift.
elementor-mcp CLAUDE.md
Claude Code instructions for msrbuilds/elementor-mcp, covering claude.md, project overview, companion projects (sibling folders, edit from here), dependencies & requirements and build & development commands.
wprig copilot-instructions.md
Copilot instructions for wprig/wprig, covering wp rig ai agents guide, 1. onboarding & state protocol, 2. architecture & build pipeline, 3. contract-first development and 4. configuration & content first.
wprig AGENTS.md
AGENTS.md instructions for wprig/wprig, covering wp rig ai agents guide, 1. onboarding & state protocol, 2. architecture & build pipeline, 3. contract-first development and 4. configuration & content first.