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/lagrowthmachine/gtm-system/claude-mdgit clone --depth 1 https://github.com/LaGrowthMachine/gtm-systemWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/lagrowthmachine/gtm-system/claude-md)<a href="https://agentmods.dev/instructions/lagrowthmachine/gtm-system/claude-md"><img src="https://agentmods.dev/badge/instructions/lagrowthmachine/gtm-system/claude-md.svg" alt="Measured on agentmods" height="20"></a>What 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.01792 | $0.01792 |
| Opus 5 | $0.00896 | $0.00896 |
| Sonnet 5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade A, and why
gtm-system CLAUDE.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 4d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LGM GTM Skills — Claude setup
You are looking at the GTM System repo maintained by La Growth Machine. It bundles a library of public Claude skills (sourcing, list building, campaigns, copywriting, analytics, reply handling) and an MCP server that lets Claude act directly inside the user's LGM workspace.
First-time setup
Check if the LGM MCP is already configured by running claude mcp list (look for a line starting with LaGrowthMachine:). The installer registers the MCP via claude mcp add --scope user --transport http, which stores the config in ~/.claude.json at user scope (available in every project). If the claude CLI isn't available, ask the user whether they've already run sh install.sh.
If it is NOT configured, proactively tell the user:
"I can see this is the LGM GTM Skills repo. Would you like me to install the LGM MCP and skills? It takes ~1 minute — I'll run
sh install.shfor you. On first use, a browser tab opens to sign in to La Growth Machine (OAuth) — new accounts can be created from that tab. No API key to copy, nothing to paste."
If they say yes, run sh install.sh and confirm when done.
If it IS configured, present the onboarding to the user:
- Confirm MCP is connected and list the available MCP tools grouped by category (Audiences, Campaigns, Inbox, Send, Workspace, LinkedIn, BigQuery).
- List the available GTM Skills grouped by category.
- Show the suggested first-steps table.
- Ask: "What would you like to do?"
What LGM gives you
Once the MCP is connected and skills are installed, two layers work together.
Layer 1 — LGM MCP (Claude acts inside La Growth Machine)
The MCP gives Claude direct access to the user's LGM workspace. No copy-paste, no tab switching. Tools are exposed under the namespace mcp__LaGrowthMachine__*.
Audiences
create_audience_from_linkedin_url— create an audience directly from a Sales Navigator search URLget_audience— fetch an existing audience by IDget_audience_leads— list all leads in an audience (paginated)
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.
- 4d ago First seen · 133 lines · 1,792 tokens per session scan A e3d3e385f1bd
gtm-system CLAUDE.md is an instructions file published in the GitHub repository LaGrowthMachine/gtm-system (34 stars, last pushed 17d ago), licensed MIT. It adds 1,792 tokens to every session, about $0.0090 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
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.