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 cogni-work/insight-wave --skill sales-enablementgit clone --depth 1 https://github.com/cogni-work/insight-waveWrote 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/cogni-work/insight-wave/sales-enablement)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/sales-enablement"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/sales-enablement/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/cogni-work/insight-wave/sales-enablement"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/sales-enablement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00115 | $0.01692 |
| Opus 5 | $0.00057 | $0.00846 |
| Sonnet 5 | $0.00023 | $0.00338 |
| Haiku 4.5 | $0.00012 | $0.00169 |
Grade A, and why
sales-enablement 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 4d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sales Enablement Content
Purpose
Generate internal-facing content that equips sales and consulting teams with the intelligence, scripts, and tools they need to close deals. Sales enablement sits at the decision stage — the prospect is evaluating specific solutions and the sales team needs competitive differentiation, objection responses, and deal-specific materials.
Prerequisites
- Marketing project with GTM paths configured
- Portfolio data: propositions, competitors, solutions, and customer profiles populated
- Recommended: portfolio compete phase completed (competitor data exists)
Input Parameters
| Parameter | Required | Description |
|---|---|---|
| market | Yes | Market slug |
| gtm_path | Yes | GTM path theme ID |
| format | No | battle-card, one-pager, demo-script, objection-handler, proposal-section. If omitted, ask |
Workflow
Step 1: Load Context
- Read
marketing-project.json— brand, language - Load portfolio data (this skill is the most portfolio-heavy):
- Competitors for this market: names, positioning, strengths, weaknesses, differentiation
- Propositions: full IS/DOES/MEANS statements
- Solutions: implementation phases, pricing tiers, effort estimates
- Packages: bundled tiers with pricing
- Customer profiles: buyer personas with pain points, buying criteria, decision roles
- Load TIPS data: solution template readiness (what the portfolio covers vs. gaps)
- Optional enrichment: If
sources.enriched_portfolio_narrativesexists inmarketing-project.json, read the market-level and persona-level customer narratives for this market. These contain pre-written buyer-facing language that strengthens objection handlers and one-pagers with tested messaging. Especially useful for the "When we win" sections in battle cards.
Step 2: Generate Content
Battle Card (400-500 words)
Structure:
- Header: Our solution vs. [Competitor Name] — for [Market]
- Quick comparison table:
| Dimension | Us | Competitor | |------------------|-----------------------|----------------------| | Core approach | [IS statement] | [Their positioning] | | Key advantage | [DOES statement] | [Their advantage] | | Customer value | [MEANS statement] | [Their value claim] | | Pricing model | [From solutions] | [From compete data] | | Readiness | [Blueprint readiness] | [Est. maturity] | - When we win: Scenarios where our solution is stronger (from portfolio differentiation)
- When they win: Honest assessment of competitor strengths (builds sales credibility)
- Trap questions: Questions to ask the prospect that expose competitor weaknesses
- Key objections: Top 3 objections when competing against this specific competitor + responses
- Proof points: Evidence from TIPS claims or portfolio case studies
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.
- 4d ago First seen · 143 lines · 115 tokens per session scan A 3529919a1f3a
sales-enablement is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 115 tokens to every session and 1,692 once invoked, about $0.0006 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-09-04.
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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…