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 enablement-forgegit 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/enablement-forge)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/enablement-forge"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/enablement-forge/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/enablement-forge"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/enablement-forge.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.00056 | $0.00860 |
| Opus 5 | $0.00028 | $0.00430 |
| Sonnet 5 | $0.00011 | $0.00172 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
enablement-forge 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 9d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enablement Forge (CRAFT System)
Production engine that takes positioning, competitive intelligence, and journey data and turns them into ready-to-use sales and marketing assets.
When to Use
- Pre-launch asset creation
- Sales team onboarding materials
- New persona/segment asset builds
- Competitive displacement campaigns
- Quarterly asset refresh
What You'll Need
Critical inputs (ask if not provided):
- Product being sold
- Target buyer persona(s)
- Sales motion (PLG, sales-led, hybrid)
Nice-to-have:
- Position Lock output (messaging backbone)
- Battle Scanner output (competitive intelligence)
- Journey Architect output (stage-specific needs)
Process
Step 1: Asset Inventory Matrix
Map required assets by journey stage x asset type:
| Asset Type | G1-G2 Awareness | G3 Consideration | G4 Conviction | G5-G7 Post-Sale |
|---|---|---|---|---|
| Pitch materials | Elevator pitch | Demo script, 1-pager | Executive deck | QBR template |
| Competitive | Category POV | Comparison sheet | Displacement guide | Competitive alert |
| Evidence | Industry report | Case study | ROI analysis | Success story |
| Technical | Architecture overview | Integration guide | Security whitepaper | API docs |
| Enablement | Discovery questions | Talk tracks | Objection handler | Expansion playbook |
| Self-service | Assessment tool | Interactive demo | ROI calculator | Health check tool |
Step 2: CRAFT Brief per Asset
For each priority asset:
| Field | What It Defines |
|---|---|
| Context | What situation triggers need for this asset? |
| Role | Who uses it? (AE, SDR, SE, CSM, prospect, marketing) |
| Asset-type | Specific format (deck, 1-pager, video script, calculator) |
| Format | Structural template with sections and word counts |
| Trigger | What event signals this asset should be deployed? |
Step 3: Asset Prioritization
Score each asset:
- Usage frequency (1-5): How often will this be used?
- Deal impact (1-5): How much does it affect win rates?
- Creation effort (1-5): How much effort to produce?
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.
- 9d ago First seen · 87 lines · 56 tokens per session scan A 3212d14565c4
enablement-forge is a skill published in the GitHub repository varunk130/ai-gtm-skill-library (5 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 860 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.
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.
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.
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…