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 Vibe-Marketer/plugins-and-skills --skill offer-definitiongit clone --depth 1 https://github.com/Vibe-Marketer/plugins-and-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/vibe-marketer/plugins-and-skills/offer-definition)<a href="https://agentmods.dev/skills/vibe-marketer/plugins-and-skills/offer-definition"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-skills/offer-definition/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/vibe-marketer/plugins-and-skills/offer-definition"><img src="https://agentmods.dev/badge/skills/vibe-marketer/plugins-and-skills/offer-definition.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.00057 | $0.01356 |
| Opus 5 | $0.00028 | $0.00678 |
| Sonnet 5 | $0.00011 | $0.00271 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
offer-definition 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<critical_distinction> This is NOT marketing copy. You are creating the pure, logical foundation upon which all future marketing will be built. Output must be bulletproof truth - simple, direct, and free of hype. If it feels salesy, rewrite it to sound like factual conversation. </critical_distinction>
<quick_start> Provide any of these materials:
- Brand/product descriptions
- Websites, landing pages, pitch decks
- Marketing transcripts, videos
- Client feedback, testimonials
I will dissect using the PVT framework to deliver:
- The Product (transformation/outcome)
- The Vehicle (delivery methods)
- The Target Market (specific buyers)
- Simple one-sentence summaries </quick_start>
- What do you sell? (Product, service, program, offer)
- What do customers get as a result? (Outcomes, transformations)
- How is it delivered? (Methods, tools, interactions)
- Who buys it? (Customer description)
- Any materials? (Optional - sales pages, testimonials, descriptions)
<core_principles> The Product is the Vacation, the Vehicle is the Airplane Never confuse end result with transport. The Product is the new reality or ability gained (outcome). The Vehicle is the practical steps or tools that get there.
Separate the "What" from the "How" "What" = Result and core system that produces it "How" = Tangible deliverables and interactions
Extract, Don't Invent Base analysis exclusively on provided materials. Pull real signal from noise. If unclear, note it and suggest gathering more data.
Simplicity and Iteration Language so clear a teenager could explain it after one read. No jargon, abstractions, or lofty phrasing.
Make It Living and Aligned This anchors everything. Ensure it matches who you actually sell to (not idealized buyers) and evolves with feedback.
Avoid Common Pitfalls Don't build one playbook if offers differ. Focus on buyer, not seller - offers sell because of customer needs, not your story. </core_principles>
Write 4-5 sentences describing the core result and system that creates it. Explain as the "new ability" customer acquires.
DO NOT mention delivery methods (calls, videos, software).
Include:
- Dream outcome achieved (specific, quantifiable)
- Proprietary system/method/framework gained (describe function without naming delivery)
- Primary quantifiable result produced
- Painful problem permanently solved
Refinement: If jargon creeps in, replace with everyday words. Check against real client transformations. </step_product>
<step_vehicle> The Vehicle (The Delivery)
Write 4-5 sentences describing tangible components and delivery experience. Explain how the Product is "installed" in practical terms.
DO NOT talk about outcomes or transformations.
Include:
- How it's delivered (e.g., "12-week series of guided steps")
- Key tangible features (e.g., "three 60-minute live sessions per week")
- Format and frequency of interaction
- Support systems included
Refinement: Avoid naming the product or outcomes. Check alignment with Product without overlap. </step_vehicle>
<step_market> The Target Market (The Who)
Write 4-5 sentences describing specific buyers in plain English. Use real-world details.
Include:
- Profession/industry and current stage (e.g., "roofing company owners with 5-20 employees making $500k-$2M")
- Urgent pain or missed opportunity that bothers them daily
- What they've tried and why it failed
- Their mindset (action-takers vs. tire-kickers)
- Where they hang out (online/offline with specific examples)
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 · 160 lines · 57 tokens per session scan A 5933ca4a0cb9
offer-definition is a skill published in the GitHub repository Vibe-Marketer/plugins-and-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 1,356 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…