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 Zevenue/headless-gtm --skill 00-gtm-routergit clone --depth 1 https://github.com/Zevenue/headless-gtmWrote 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/zevenue/headless-gtm/00-gtm-router)<a href="https://agentmods.dev/skills/zevenue/headless-gtm/00-gtm-router"><img src="https://agentmods.dev/badge/skills/zevenue/headless-gtm/00-gtm-router/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/zevenue/headless-gtm/00-gtm-router"><img src="https://agentmods.dev/badge/skills/zevenue/headless-gtm/00-gtm-router.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00270 | $0.04313 |
| Opus 5 | $0.00135 | $0.02157 |
| Sonnet 5 | $0.00054 | $0.00863 |
| Haiku 4.5 | $0.00027 | $0.00431 |
Grade A, and why
00-gtm-router 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM Router - the orchestrator (00)
Every other skill in this chain wraps a tool. This one wraps the decision: given an ICP, which chain do you run, in what order, at what depth, and what will it cost. Tool-routing ("use Firecrawl for scraping") is table stakes; this skill does methodology-routing - the shape of the ICP picks the discovery path, volume picks the extraction depth, evidence type picks the signal source, every discovered list passes the qualification gate (01-icp-qualify) before credits are spent on it, and everything funnels through judgment (05) before anyone writes an email. Two model-judgment layers bracket the paid steps: the gate decides who is worth paying to know more about, the judge decides what to say to them.
The router itself spends nothing. All credits are spent inside component skills, each of which keeps its own spend gates. The router's job is to make the spend deliberate: plan first, estimate honestly, execute only after a go-ahead, and checkpoint between steps.
Inputs
- icp_description (required) - who the client is targeting, in plain English.
- icp_context - what the client sells, to whom, and what pain it removes (2-4 sentences). 05-signal-builder cannot judge without it, so collect it during planning, not four steps in. If it's missing, ask once.
- exclusions (optional, ask once) - competitors, current customers, do-not-contact domains. The gate (01-icp-qualify) enforces them for free; discovery skills also apply them as filters where supported.
- budget_ceiling, target_volume, urgency (optional) - shape the plan. Missing values don't block planning: assume, label the assumption, and show the math so the user can correct it.
Start where the data runs out
Discovery is only step one if the user has nothing. Route to the first step whose input is missing:
| User already has | Enter the chain at |
|---|---|
| Nothing yet - no list, no CRM, first campaign ever | run-first-campaign - the packaged cold-start workflow (context -> source of record -> gate -> rank -> drafts -> sheet, owner approval between steps) |
| Nothing but an ICP description | Discovery (01-prospeo-discover, 02, or 04-theirstack discover, by shape below) |
| Example companies to find more of | 01-prospeo-lookalike - the list is seeds, not targets |
| A target company list (domains) | 01-icp-qualify first, then 03/04 on the survivors |
| A list with scrape/signal data | 05-signal-builder |
| Named contacts missing emails | 06-resolution-email-person |
| Signals + verified emails | email-writer (the chain is done) |
What ships with it
3 files 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 · 286 lines · 270 tokens per session scan A b5b907697a8f
00-gtm-router is a skill published in the GitHub repository Zevenue/headless-gtm (27 stars, last pushed 1mo ago), licensed MIT. It adds 270 tokens to every session and 4,313 once invoked, about $0.0014 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
gtm-machine
Validate startup ideas with evidence and test them with real outbound — the full loop from raw idea to booked calls. Use this skill whenever an idea-stage founder wants to validate a startup or product idea, assess AI-platform kill-risk, check if a market is worth entering, build an ICP or personas, source leads from…
deepline-ads-audiences
Use this skill when building, enriching, auditing, or uploading B2B paid ads audiences to Google Customer Match, Meta/Facebook Custom Audiences, or LinkedIn Matched Audiences. Triggers on phrases like '/deepline-ads-audience', '/deepline-ads-audiences', 'upload this audience', 'create custom audiences', 'personal…
deepline-gtm
GTM prospecting, enrichment, outreach, and Deepline Play work/audits. Providers…
deepline-pre-research
Use when the user wants a last30days-style pre-research pass in Deepline: discover the critical public, private, CRM, workflow, social, and web data sources for a research/enrichment job; compare provider coverage; estimate Deepline credit cost; recommend the source plan before building or running the workflow; or…
deepline-analytics
Use this skill when answering business analytics, RevOps, GTM metric, pipeline, revenue, funnel, customer, or warehouse questions with Deepline. Triggers on phrases like 'query Snowflake', 'analyze pipeline', 'total ACV', 'break down by quarter', 'use the semantic layer', 'run a semantic query', or any use of…
niche-signal-discovery
Discover niche first-party signals that differentiate Closed Won vs Closed Lost accounts for ICP analysis. Use when the user provides won/lost customer domain lists and wants differential signals (website content, job listings, tech stack, maturity markers) to build account scoring models and prospecting criteria.…