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 skills add varunk130/ai-gtm-skill-library --skill gtm-exec-plangit clone --depth 1 https://github.com/varunk130/ai-gtm-skill-libraryWrote 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/skills/varunk130/ai-gtm-skill-library/gtm-exec-plan)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/gtm-exec-plan"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/gtm-exec-plan/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/skills/varunk130/ai-gtm-skill-library/gtm-exec-plan"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/gtm-exec-plan.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.00108 | $0.01915 |
| Opus 5 | $0.00054 | $0.00958 |
| Sonnet 5 | $0.00022 | $0.00383 |
| Haiku 4.5 | $0.00011 | $0.00192 |
Grade A, and why
gtm-exec-plan 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Exec Plan (PRIME Framework)
Create a polished, executive-ready Go-To-Market brief (3-4 pages) and a 4-slide GTM PowerPoint deck for any new product, feature, or platform initiative. PRIME synthesizes insights from across the GTM skill library into two high-impact deliverables that are ready for leadership review.
When to Use
- Presenting a GTM strategy to leadership or a steering committee
- Kicking off a new product launch and need an executive-ready plan
- Preparing a GTM strategy for a platform play (e.g., ACME Insight Studio, API ecosystem)
- Board or investor readiness for a go-to-market motion
- Quarterly GTM refresh for an existing product line
- Cross-functional alignment on a launch strategy
What You'll Need
Critical inputs (ask if not provided):
- Product or feature name
- One-sentence value proposition
- Target audience (persona, segment, industry)
- Launch timeline or target date
- Top 3 competitors
Nice-to-have (will enrich the output):
- Outputs from other skills:
market-analyzer,position-lock,battle-scanner,demand-engine - Pricing model or tier structure
- Internal stakeholder priorities or constraints
- Partner or ecosystem context
- Win/loss data or customer feedback themes
PRIME Framework
The brief and deck are organized around five executive sections:
| Section | What It Covers | Brief Length | Deck Presence |
|---|---|---|---|
| Positioning | Why this product wins: value prop, differentiation, messaging hierarchy | ~1 page | Slide 2 |
| Readiness | Market context, competitive landscape, timing rationale | ~0.5 page | Slide 2 |
| Impact | Revenue model, target metrics, success criteria, projected outcomes | ~0.5 page | Slide 3 |
| Motion | Channel strategy, demand gen approach, partner leverage, enablement plan | ~1 page | Slide 3 |
| Execution | Phased timeline, milestones, owners, go/no-go gates | ~0.5 page | Slide 4 |
Process
Step 1: Gather and Synthesize Inputs
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 First seen · 175 lines · 108 tokens per session scan A e3a550ee8c36
gtm-exec-plan is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (6 stars, last pushed 1mo ago), licensed MIT. It adds 108 tokens to every session and 1,915 once invoked, about $0.0005 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-31.
Other skills, from other repositories
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
110-java-maven-best-practices
Use when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module project structure, build profiles, or any situation where you want to align your Maven setup with industry best practices. This should…