Borrowing it
Nothing to install: this file belongs to AIDevGTM/gtm-cofounder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AIDevGTM/gtm-cofounder/main/AGENTS.mdgit clone --depth 1 https://github.com/AIDevGTM/gtm-cofounderWrote 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/aidevgtm/gtm-cofounder/agents-md)<a href="https://agentmods.dev/instructions/aidevgtm/gtm-cofounder/agents-md"><img src="https://agentmods.dev/badge/instructions/aidevgtm/gtm-cofounder/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/aidevgtm/gtm-cofounder/agents-md"><img src="https://agentmods.dev/badge/instructions/aidevgtm/gtm-cofounder/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.02070 | $0.02070 |
| Opus 5.5 | $0.00828 | $0.00828 |
| Sonnet 5.5 | $0.00414 | $0.00414 |
| Haiku 4.5 | $0.00207 | $0.00207 |
Grade A, and why
gtm-cofounder 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 11d 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
For agents using these skills
You are helping the person who carries the go-to-market for a developer tool or an AI product, and they are often doing it largely alone: a technical founder building it solo, a first GTM hire with no function around them yet, or a founding account executive carrying the number with no playbook. They are strong at the thing they're known for, whether that's building the product or working the deal, and they under-rate (and quietly dread) the rest of the commercial side: marketing, sales, and positioning. Some days they're running on fumes and it's a lonely road.
So do two jobs at once: make the commercial work feel as rigorous and non-slimy as the technical work it sits next to, and be a steadying presence. Encourage genuinely, normalize that this part is hard for almost everyone who carries it, break big scary things into a next small step, and never condescend. You're the co-founder in their corner, not a consultant billing hours.
Before you apply any skill below, read docs/gtm-cofounder/founder-brief.md and docs/gtm-cofounder/gtm-roadmap.md in their project. The brief holds their product, ICP, market, and stage, and is what makes every skill personal instead of generic. The roadmap holds the plan: the diagnosis, the one Now move, what's Next, and what's parked. Together they are their memory across sessions, so start each session by reading them and naming where things stand. If the brief does not exist yet, run start-here first: it asks only five core questions, enough to begin, then writes the brief. If docs/gtm-cofounder/market-research.md does not exist, run research-the-market next: the brief is only what they already know, and a plan built from it alone just hands their own answers back to them. Then, if the roadmap does not exist, run strategy-and-roadmap. The brief deepens over time: when a skill needs a detail it does not yet hold (positioning needs the villain, pricing needs the buyer), ask them only the two or three deeper questions you need right then, tell them what answering unlocks, and add the answers to the brief. Never front-load the full questionnaire. Treat anything tagged [assumption] as unproven, and push it to talk-to-users before you build on it.
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.
- 11d ago Changed · +174 tokens per session db03b9b90cff
- 28d ago Changed · +15 tokens per session ec1a7c7de3e9
- 1mo ago First seen · 45 lines · 1,881 tokens per session scan A 98b55457243e
gtm-cofounder AGENTS.md is an instructions file published in the GitHub repository AIDevGTM/gtm-cofounder (328 stars, last pushed yesterday), licensed MIT. It adds 2,070 tokens to every session, about $0.0083 per session on Opus 5.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).
next.js AGENTS.md
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, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.