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 matellez/claude-skills --skill partner-marketing-infrastructuregit clone --depth 1 https://github.com/matellez/claude-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/matellez/claude-skills/partner-marketing-infrastructure)<a href="https://agentmods.dev/skills/matellez/claude-skills/partner-marketing-infrastructure"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/partner-marketing-infrastructure/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/matellez/claude-skills/partner-marketing-infrastructure"><img src="https://agentmods.dev/badge/skills/matellez/claude-skills/partner-marketing-infrastructure.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.00201 | $0.03365 |
| Opus 5 | $0.00101 | $0.01682 |
| Sonnet 5 | $0.00040 | $0.00673 |
| Haiku 4.5 | $0.00020 | $0.00336 |
Grade A, and why
partner-marketing-infrastructure 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- partner-marketing-infrastructure — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Partner Marketing Infrastructure: Building and Attributing Partner Pipeline
This skill designs the operational infrastructure of a B2B partner program: tier structure, pipeline attribution, joint go-to-market execution, and measurement framework. Most partner programs fail not because the partners are wrong but because the infrastructure is missing. Partners without a clear tier structure get inconsistent treatment. Partner-sourced deals without attribution get credited to the wrong channel. Programs without a measurement framework get cut when budgets tighten because no one can prove their value.
HOW TO SET UP THIS SKILL
This skill works out of the box. For more specific output, provide:
- Type of partners: technology integrations, resellers, referral partners, system integrators, or a combination
- Current state: no program exists, a program exists but is informal, or a program exists and needs to be rebuilt
- Number of current or target partners
- Average deal size and sales cycle length for the core product
- Whether the CRM is HubSpot, Salesforce, or another system
- Whether sales has separate pipeline targets for partner-sourced deals
The Four Partner Program Infrastructure Problems
Most partner programs that underperform have one of four structural problems. Identify which applies before building anything.
Problem 1: No tier structure, so all partners get the same treatment
The company has twenty partners. Three of them refer deals consistently. Five refer a deal every few months. Twelve have never referred a deal but attend the annual partner summit. All twenty receive the same co-marketing budget, the same sales attention, and the same access to product roadmap information.
The result: the three high-performing partners feel undervalued relative to the investment required to maintain the program. The twelve inactive partners consume resources without producing pipeline. Everyone is dissatisfied.
Fix: Build a tier structure that allocates resources based on partner performance and potential. Tiers define what partners receive (sales support, co-marketing budget, product access, deal registration protection) and what they are expected to produce in return (pipeline volume, deal size, customer success outcomes).
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 · 392 lines · 201 tokens per session scan A 1427e15423ce
partner-marketing-infrastructure is a skill published in the GitHub repository matellez/claude-skills (4 stars, last pushed 5mo ago), licensed MIT. It adds 201 tokens to every session and 3,365 once invoked, about $0.0010 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
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
market-research-workflow
Trigger for: federal acquisition market research; FAR Part 10 reports; refreshing an existing market research report; analyzing commerciality, competition, small-business availability, contract type, consolidation, prior awards, vendors, or market conditions; or preparing supported findings for a Pre-Award Agent. A…
acquisition-policy-workflow
Trigger for: explaining current FAR, DFARS, or agency-supplement text; determining documented acquisition-policy status for an agency and FAR part; comparing codified text, RFO model text, and agency deviations; tracing acquisition rulemaking; finding procurement comment periods; analyzing public comments; refreshing…
igce-builder-lh-tm
Trigger for: Labor-Hour IGCE, LH estimate, Time-and-Materials IGCE, T&M estimate, burdened hourly rate, burden multiplier, labor-category ceiling hours, materials estimate, proposed LH/T&M rate validation, price-reasonableness memo, or fair-and-reasonable analysis. Build auditable LH/T&M estimates using BLS OEWS…
rudder-data-graphs
Produces Data Graph YAML from RETL sources for Audiences. Use when designing Data Graphs, mapping RETL to entities/events, or assessing customer fit for Audiences.
rudder-typer-workflow
Generates type-safe SDKs (Swift/Kotlin) from tracking plans with compile-time validation. Use when generating type-safe event tracking code from tracking plans using RudderTyper.