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 thought-leadershipgit 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/thought-leadership)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/thought-leadership"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/thought-leadership/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/thought-leadership"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/thought-leadership.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.00119 | $0.01852 |
| Opus 5 | $0.00060 | $0.00926 |
| Sonnet 5 | $0.00024 | $0.00370 |
| Haiku 4.5 | $0.00012 | $0.00185 |
Grade A, and why
thought-leadership 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thought Leadership Content Generation
Purpose
Generate expert-positioning content that leverages TIPS trend analysis (WHY NOW) and portfolio authority (WHAT WE KNOW) to establish the brand as a trusted voice. Thought leadership lives at the top of funnel — it educates, provokes, and builds credibility without hard selling.
Prerequisites
- Marketing project with at least one GTM path configured
- Content strategy recommended (but not required — can generate ad-hoc)
Input Parameters
| Parameter | Required | Description |
|---|---|---|
| market | Yes | Market slug (determines language, persona, proposition context) |
| gtm_path | Yes | GTM path theme ID (determines trend narrative) |
| format | No | Specific format: blog, linkedin-article, keynote-abstract, podcast-outline, op-ed. If omitted, ask user |
Workflow
Step 1: Load Context
- Read
marketing-project.json— extract brand voice, tone modifiers, content defaults, language - Read
content-strategy.json— find the narrative angle for this market × GTM path cell - Load TIPS data for the GTM path:
- Strategic theme narrative (from
tips-value-model.json) - Top 3 trend candidates in the theme's value chains (from
trend-scout-output.json) - Relevant claims with evidence (from
tips-trend-report-claims.json)
- Strategic theme narrative (from
- Load portfolio context:
- Propositions for this market (IS/DOES/MEANS — for domain authority, not sales pitch)
- Company positioning (from
portfolio.json)
- Optional enrichment: If
sources.enriched_portfolio_narrativesexists inmarketing-project.json, read the market-level customer narrative for this market. Use it as a voice and messaging reference — it contains pre-written audience-tailored language that helps maintain consistency between portfolio communication and marketing content. Do not copy verbatim; use it to inform tone and framing.
Step 2: Select Format
If format not specified, present options with recommendations:
Thought leadership formats for {market} × {gtm_path}:
1. blog (800-1200w) — Recommended as anchor content
2. linkedin-article (600-800w) — Good for professional reach
3. keynote-abstract (150-200w) — If speaking engagement planned
4. podcast-outline (400-500w) — If podcast channel active
5. op-ed (600-800w) — If publishing in industry media
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 Changed · -1 lines ecb1570d47e2
- 8d ago First seen · 156 lines · 119 tokens per session scan A b809ae27aefc
thought-leadership is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 119 tokens to every session and 1,852 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…