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 modest-curator478/claude-skills --skill partner-marketing-infrastructuregit clone --depth 1 https://github.com/modest-curator478/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/modest-curator478/claude-skills/partner-marketing-infrastructure)<a href="https://agentmods.dev/skills/modest-curator478/claude-skills/partner-marketing-infrastructure"><img src="https://agentmods.dev/badge/skills/modest-curator478/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/modest-curator478/claude-skills/partner-marketing-infrastructure"><img src="https://agentmods.dev/badge/skills/modest-curator478/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.
This is a copy
100% identical to partner-marketing-infrastructure — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 modest-curator478/claude-skills (4 stars, last pushed yesterday), 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. It is 100% identical to partner-marketing-infrastructure, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
TEMPLATE
../../../agents/personas/TEMPLATE.md.
debug
Systematic debugging using error-detective and debugger agents instead of manual investigation. Triggers automatically on: error, bug, broken, failing, exception, stack trace, test failure. Orchestrates RCA-first approach with parallel agent investigation.
deep-context
Build deep codebase understanding using Capsule context, progressive-reader, and specialist agents instead of overwhelming main context. Triggers on: don't have context, understand codebase, learn about, need background. Implements progressive context building.
workflow
Systematic task orchestration for complex multi-step tasks. Triggers automatically when detecting: complex task, multi-step work, coordinate, orchestrate, break down. Guides through Understand → Strategy → Plan → Execute → Verify phases for comprehensive systematic approach.
task-router
Decision matrix for choosing optimal approach to any task. Helps Claude decide when to delegate to sub-agents vs. working directly. Use when starting a new task or unsure of best approach.
nextdns-cli
NextDNS CLI client best practices for installation, configuration, and management of DNS-over-HTTPS proxy. This skill should be used when installing NextDNS on routers, servers, or client devices, configuring DNS settings, managing the daemon, or troubleshooting DNS issues. Triggers on tasks involving NextDNS CLI…