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 partner-blueprintgit 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/partner-blueprint)<a href="https://agentmods.dev/skills/varunk130/ai-gtm-skill-library/partner-blueprint"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/partner-blueprint/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/partner-blueprint"><img src="https://agentmods.dev/badge/skills/varunk130/ai-gtm-skill-library/partner-blueprint.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.01020 |
| Opus 5 | $0.00026 | $0.00510 |
| Sonnet 5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
partner-blueprint 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Partner Blueprint (BRIDGE Framework)
Engineer partnership strategy from identification through activation. Partnerships are a multiplier, not just a channel.
When to Use
- Building partner/channel program from scratch
- Evaluating specific partnership opportunity
- Designing co-GTM with existing partner
- Expanding into new geography via partners
- Platform/ecosystem strategy
What You'll Need
Critical inputs (ask if not provided):
- Your product and target market
- Partnership goals (reach, credibility, technology, revenue)
- Current partner landscape (if any)
Nice-to-have:
- Battle Scanner output (competitor partnerships to counter)
- Market Analyzer output (segments needing partner reach)
Process
Step 1: Partner Landscape Mapping
Identify candidates across 6 categories:
| Category | What They Offer | Examples |
|---|---|---|
| Technology | Integrations, platform plays | CRM, cloud providers, data platforms |
| Channel/Reseller | Reach into new segments/geos | VARs, MSPs, regional resellers |
| Co-marketing | Audience sharing, content collab | Complementary SaaS, media partners |
| Implementation | Consulting, deployment, training | SIs, boutique consultancies |
| Strategic/OEM | Embedded, white-label | Enterprise platforms, industry solutions |
| Community/Ecosystem | Developer communities, associations | Open-source projects, industry groups |
Step 2: BRIDGE Scoring (per partner candidate, 1-10 each)
| Dimension | What It Measures | Scoring Guide |
|---|---|---|
| Business-fit | Strategic alignment of customers and goals | 1=no overlap, 5=partial, 10=perfect alignment |
| Reach | Incremental access to markets you cannot reach alone | 1=same audience, 5=some new, 10=opens new markets |
| Investment | Required time, money, engineering (inverse) | 1=massive investment, 5=moderate, 10=minimal |
| Dependencies | Risk of dependency (inverse) | 1=total dependency, 5=balanced, 10=no risk |
| Growth-potential | Can this scale? Network effects? | 1=one-time, 5=linear growth, 10=exponential |
| Execution-readiness | Team, processes, motivation to execute now | 1=not ready, 5=needs work, 10=ready to go |
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 · 86 lines · 51 tokens per session scan A bedaec5b6608
partner-blueprint 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,020 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…