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/growthkit-tools/mcp/agents-mdgit clone --depth 1 https://github.com/growthkit-tools/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.20863 | $0.20863 |
| Opus 5 | $0.10431 | $0.10431 |
| Sonnet 5 | $0.04173 | $0.04173 |
| Haiku 4.5 | $0.02086 | $0.02086 |
Grade B, and why
mcp AGENTS.md scanned grade B with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Die Regel wurde am 21.08. aus `~/.claude/settings.json` entfernt — nicht Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| zsh-Schleifenvariable `path` | „33 von 33 Abweichungen" | `path` ist an `PATH` gebunden; `curl` war nach der ersten Zeile nicht mehr auffindbar | How it starts
The opening of the file, as written. The whole thing — 1,157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GrowthKit MCP Worker — Agent Quick Reference
Ablage: Repo-Root als
AGENTS.md. Danachgit rm CLAUDE.md && ln -s AGENTS.md CLAUDE.md— eine Quelle, zwei Namen. Zwei getrennte Guide-Dateien driften auseinander.Prinzip: Jede Zeile geht auf einen beobachteten Fehler oder eine reale Invariante zurück. Neue Zeilen nur bei echtem Anlass. Zeilen ohne Anlass sind Rauschen.
⚠️ TODO= gegen das Repo verifizieren.🔵 ENTSCHEIDUNG= Chris muss bestätigen.
Wissen
Cloudflare Worker, serviert den GrowthKit MCP-Server auf mcp.growthkit.tools.
- Ein hand-rolled File:
index.js, ~4200 Zeilen (Stand 24.08.2026). MCP JSON-RPC manuell implementiert, kein SDK.tools/list,tools/call,resources/list,resources/read, Prompts und OAuth sind alle von Hand gebaut. Es gibt keine Bibliothek, die Fehler abfängt. - Konsumenten: Claude (Desktop/Web/Code), ChatGPT, MCP-Registries. Regressionen brechen still — kein Alert, nur sinkende Nutzung. Deshalb ist der Golden Master nicht optional.
- Backend: Supabase-Projekt (EU Frankfurt) über Edge Functions,
Custom Domain
api.growthkit.toolsproxied/functions/v1/*. Project-Ref steht inwrangler.toml/ den Worker-Secrets, nicht hier. - Auth: Zwei Auflösungswege, unterschieden allein am Token-Präfix (
index.js~1321). Die Entscheidung fällt vor jedem Backend-Aufruf.- Bearer beginnt mit
gk_→ direkter API-Token-Pfad:resolve_user_tokengegenuser_api_tokens; die RPC hasht selbst und prüftis_active. Kein OAuth, kein Browser — das ist der Pfad für Tests, CI und Automatisierung. Zwei bewusste Nicht-Handlungen:last_used_atbleibt ungeschrieben (resolve_user_tokenschreibt nicht, das tut nuruse_api_token), Tokens sehen über diesen Weg also unbenutzt aus; undisDemoist hier immerfalse—user_api_tokenshat keinis_demo, Demo-Sessions laufen ausschließlich über OAuth. - Alles andere → OAuth-Pfad wie bisher: gegen
oauth_tokens.access_tokenmit Ablaufprüfung; dasgk_-Token liegt dort alsuser_token.
- Bearer beginnt mit
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 · 1,157 lines · 20,863 tokens per session scan B 06855886fc72
mcp AGENTS.md is an instructions file published in the GitHub repository growthkit-tools/mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 20,863 tokens to every session, about $0.1043 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). 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.
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.