Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add cogni-work/insight-wave/plugin install cogni-marketingWrote 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/marketing-setup)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/marketing-setup"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/marketing-setup.svg" alt="Measured on agentmods" 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.00093 | $0.01661 |
| Opus 5 | $0.00046 | $0.00830 |
| Sonnet 5 | $0.00019 | $0.00332 |
| Haiku 4.5 | $0.00009 | $0.00166 |
Grade A, and why
marketing-setup 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 3d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marketing Setup
Purpose
Initialize a cogni-marketing project by:
- Discovering available cogni-trends and cogni-portfolio projects
- Configuring brand identity and voice
- Selecting target markets from portfolio
- Mapping TIPS strategic themes to GTM paths per market
- Scaffolding the project directory
Prerequisites
- At least one cogni-portfolio project with products, features, and markets defined
- At least one cogni-trends project with value-modeler completed (strategic themes + ranked solution templates)
Workflow
Step 0: Project Discovery
Scan the working directory for existing sources:
- Find cogni-portfolio projects: Glob for
**/portfolio.jsonfiles. For each, read to confirm it hasproductsandmarketspopulated. - Find cogni-trends projects: Glob for
**/tips-project.jsonfiles. For each, check thattips-value-model.jsonexists alongside it (value-modeler completed). - Find existing marketing projects: Glob for
**/marketing-project.jsonto avoid duplicates. - Find portfolio-communicate output (optional enrichment): For each discovered portfolio project, check if
output/communicate/customer-narrative/exists. If it does, list the files found (overview, market-level, customer-level narratives). These are pre-written audience-tailored narratives that content generation skills can reference for richer voice and messaging consistency. Store discovered paths inmarketing-project.jsonundersources.enriched_portfolio_narratives.
Present discovered sources to user:
Portfolio projects found:
1. acme-cloud (4 products, 3 markets, 12 propositions)
└─ Customer narratives: 1 overview, 3 market, 5 persona (enrichment available)
2. beta-services (2 products, 1 market, 4 propositions)
TIPS projects found:
1. b2b-ict-ai-trends (5 themes, 18 solution templates)
2. manufacturing-digital (4 themes, 12 solution templates)
If customer narratives were found, note this briefly — they will be available as optional enrichment for content generation skills (voice consistency, messaging alignment).
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.
- 3d ago First seen · 146 lines · 93 tokens per session scan A 80560c45bd38
marketing-setup is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 93 tokens to every session and 1,661 once invoked, about $0.0005 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.