Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/andrewvaughan/agent-councilnpx agentmods add skills/andrewvaughan/agent-council/gtm-reviewWrote 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/andrewvaughan/agent-council/gtm-review)<a href="https://agentmods.dev/skills/andrewvaughan/agent-council/gtm-review"><img src="https://agentmods.dev/badge/skills/andrewvaughan/agent-council/gtm-review/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/andrewvaughan/agent-council/gtm-review"><img src="https://agentmods.dev/badge/skills/andrewvaughan/agent-council/gtm-review.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.00059 | $0.04664 |
| Opus 5 | $0.00030 | $0.02332 |
| Sonnet 5 | $0.00012 | $0.00933 |
| Haiku 4.5 | $0.00006 | $0.00466 |
Grade A, and why
gtm-review 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 12d 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 — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Review Workflow
Run a comprehensive Go-to-Market and launch readiness review for a project phase. This skill audits marketing content accuracy, code quality, performance, accessibility, infrastructure readiness, and business positioning, then activates the GTM Council for a consolidated launch readiness verdict.
Scope
| Does | Does NOT do |
|---|---|
| Comprehensive phase readiness audit | Write application code or fix bugs |
| Marketing content accuracy review | Push to remote or create PRs |
| Code quality review via Review Council | Modify the project board schedule |
| Performance and accessibility audit | Re-plan features (that's /plan-feature) |
| Business and competitive analysis | Run security audit (that's /security-audit) |
Generate GTM report in docs/decisions/ |
|
| Update GTM issue with findings |
[!IMPORTANT] This skill does NOT replace the
/security-auditgate. Security audit is a separate gate item that runs after the GTM review. This skill delegates security concerns to that skill rather than duplicating its work.
Step 0: Verify Clean Working Tree
This skill commits a report file in Step 10. Ensure the working tree is clean before starting:
git status --porcelain
If there are uncommitted changes, warn the user and ask whether to stash them (git stash push -m "gtm-review: stash before review") or abort.
Step 1: Identify Phase Scope
Accept input from the user:
- GTM issue number (e.g.,
#132) — primary input - Phase identifier (e.g.,
M1) — alternative input
If given a GTM issue number:
gh issue view <number> --json title,body,labels,milestone
If given a phase identifier, find the GTM issue for that phase:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 486 lines · 59 tokens per session scan A e4800290cc51
gtm-review is a skill published in the GitHub repository andrewvaughan/agent-council (13 stars, last pushed 6mo ago), licensed MIT. It adds 59 tokens to every session and 4,664 once invoked, about $0.0003 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 skills, from other repositories
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
ralph-memory
Manage Al semantic memory entries — list, query, and clear lessons learned across loop iterations.
config-validator
Validate AIWG configuration files and project setup for correctness and completeness.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.
summarize-transcript
Analyze and summarize a transcript, meeting notes, or discussion thread into a clear actionable document.
validate-addon
Validate an entire AIWG addon package for completeness and release readiness.