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 journey-architectgit 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/journey-architect)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/journey-architect"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/journey-architect/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/journey-architect"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/journey-architect.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.00051 | $0.01050 |
| Opus 5 | $0.00026 | $0.00525 |
| Sonnet 5 | $0.00010 | $0.00210 |
| Haiku 4.5 | $0.00005 | $0.00105 |
Grade A, and why
journey-architect 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journey Architect (7-GATE Model)
Design the complete customer journey with measurable gates. Maps every touchpoint from first awareness through purchase, activation, and advocacy with friction scoring at each stage.
When to Use
- Pre-launch journey design
- Conversion funnel optimization
- Content strategy planning
- Sales process design
- Customer experience improvement
What You'll Need
Critical inputs (ask if not provided):
- Product/service being mapped
- Primary buyer persona(s)
- Current sales motion (PLG, sales-led, hybrid)
Nice-to-have:
- Market Analyzer segment data
- Existing funnel metrics
- Customer feedback or interview data
Process
Step 1: Define the 7 Gates
Each gate represents a cognitive/behavioral milestone customers must pass through:
| Gate | Name | Customer State | Key Question They Ask |
|---|---|---|---|
| G1 | Awakening | Recognizes they have a problem | "Is this actually a problem worth solving?" |
| G2 | Exploration | Begins researching solutions | "What options exist to solve this?" |
| G3 | Consideration | Builds a shortlist | "Which 2-3 solutions should I evaluate seriously?" |
| G4 | Conviction | Commits to a solution | "Can I justify this purchase internally?" |
| G5 | Activation | Starts using the product | "How do I get value from this quickly?" |
| G6 | Integration | Product becomes embedded in workflow | "How does this fit into everything else I do?" |
| G7 | Amplification | Becomes an advocate | "Who else needs to know about this?" |
Step 2: Per-Gate Analysis
For EACH gate, document:
Entry Trigger: What event causes the customer to enter this gate?
- Example G1: "Budget review reveals 30% waste in current tooling"
Information Needs: What content/evidence do they need?
- Example G3: "Feature comparison matrix, pricing transparency, peer reviews"
Touchpoints: Where do they interact?
- Example G2: "Web search, peer communities, review sites, analyst reports"
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 · 97 lines · 51 tokens per session scan A bc0ea7beb24a
journey-architect is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (6 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,050 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-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.
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.
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.
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…