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 eliasstravik/gtm-skills --skill gtm-icpgit clone --depth 1 https://github.com/eliasstravik/gtm-skillsWrote 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/eliasstravik/gtm-skills/gtm-icp)<a href="https://agentmods.dev/skills/eliasstravik/gtm-skills/gtm-icp"><img src="https://agentmods.dev/badge/skills/eliasstravik/gtm-skills/gtm-icp/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/eliasstravik/gtm-skills/gtm-icp"><img src="https://agentmods.dev/badge/skills/eliasstravik/gtm-skills/gtm-icp.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.00075 | $0.01148 |
| Opus 5 | $0.00037 | $0.00574 |
| Sonnet 5 | $0.00015 | $0.00230 |
| Haiku 4.5 | $0.00007 | $0.00115 |
Grade A, and why
gtm-icp 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 today.
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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GTM ICP
Trigger
Apply this Lifecycle SOP when the requested outcome creates, updates, repairs, or retires an ideal customer profile owned by an organization node in an existing GTM workspace.
Scope
Own node-local, freeform Markdown ICPs at icps/<icp-slug>/ICP.md across creation, refinement, deletion, and repo-wide ICP integrity repair. Create and fully research ICPs with the shared company-data contract, interpreted as desired or accepted account criteria. Read legacy icps/<icp-slug>.md artifacts without requiring migration. Do not author persona or member files, manage the workspace lifecycle, or classify/research accounts against saved ICPs.
Contract
| Field | Public contract |
|---|---|
| Reads | Accepted ICP facts and uncertainty, the root-to-owner ORG.md chain, owner-local ICPs, and safe supplied sources |
| Writes | Only the selected owner's canonical ICP path, or scoped ICP repairs during doctor |
| Outputs | An accepted node-owned ICP identified by display name and owner chain, a complete health report, or a scoped handoff |
| Approval | The agent prepares, stages, inspects, and commits the scoped change locally, then the user approves one plain-language card immediately before the push |
| Persists | Accepted ICP files in main Git history; no hidden coordination state |
| Handoff | gtm-workspace for repository structure or connections, gtm-persona for buyers, and gtm-workflow for saved operational work |
Inputs
Use the user's accepted ICP facts and uncertainty, the hosting environment's connected-repo and durable-write declarations, the root-to-owner ORG.md chain, owner-local ICPs, and safe supplied sources.
Roles
The agent owns the selected ICP lifecycle flow. The user approves one plain-language card immediately before the push that saves the prepared local commit. gtm-workspace owns repository structure and connections.
Procedure
| Condition | Owned flow |
|---|---|
| The requested outcome belongs to a sibling workflow | Hand off before workspace resolution or artifact reads; mutate nothing |
| No lifecycle verb is clear | Guide the ICP lifecycle menu and retain ownership of the selected flow |
| Create or define is requested | Resolve the workspace and owner node, ground one or many factual drafts, check owner-local overlap, describe them, and save the accepted ICPs together |
| Update or refine is requested | Resolve one visible ICP, preserve unrelated facts, describe the change, and save the accepted revision |
| Delete is requested | Resolve one visible ICP, describe ownership and consequences, remove only the accepted target, and say it can be restored on request |
| Doctor is requested or ICP artifacts seem malformed | Inspect ICP placement and content repo-wide, describe the repair set, save it once, and report resulting health |
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.
- today Changed 8321266d081b
- yesterday Changed 7087a8004426
- 3d ago Changed · +1 lines 1985e7310bea
- 8d ago Changed · +14 tokens per session 6f6f757ddde9
- 12d ago First seen · 68 lines · 61 tokens per session scan A 66bc85703f58
gtm-icp is a skill published in the GitHub repository eliasstravik/gtm-skills (12 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 1,148 once invoked, about $0.0004 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
startup-launch-playbook
A step-by-step playbook for early-stage startups going from pre-seed to their first 1000 users. Covers MVP validation, initial traction channels, and founder-led growth tactics. By @WeiYipei — follow on X for more startup growth insights.
google-tag-manager
Skill "google-tag-manager" from VKirill/claude-lane-stack, covering 🎯 version requirements (june 2026), usage, use this skill when, do not use this skill when and purpose.
gtm-reverse-engineer
Reverse-engineer any company's public go-to-market into an evidence-graded, multi-file playbook (copy / adapt / skip). Use whenever the user wants competitor GTM teardown, growth forensics, channel analysis (Instagram, X/Twitter, LinkedIn, ads, Reddit/community, SEO, jobs, pricing), "how did X grow", unicorn/breakout…
growth-marketer
!cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat .production-grade.yaml 2>/dev/null || echo "No config — using defaults".
gtm-brain-builder
Orchestrate the creation or maintenance of a source-backed GTM brain for a company, including tool connection, section routing, Grill-me questions, session relay, section-agent sequencing, and recurring freshness workflows. Use when a user wants to build a GTM Brain or make one shareable/useful for sales, marketing…
design-system-agent
Create a source-backed design-system brief and walk an operator through using Claude.ai/design or Codex design workflows to generate, review, export, and import a brand kit/design system into the GTM Brain.