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 content-calendargit 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/content-calendar)<a href="https://agentmods.dev/skills/cogni-work/insight-wave/content-calendar"><img src="https://agentmods.dev/badge/skills/cogni-work/insight-wave/content-calendar.svg" alt="Measured on agentmods" 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.00084 | $0.01222 |
| Opus 5 | $0.00042 | $0.00611 |
| Sonnet 5 | $0.00017 | $0.00244 |
| Haiku 4.5 | $0.00008 | $0.00122 |
Grade A, and why
content-calendar 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Calendar
Purpose
Generate a structured editorial calendar from the content strategy and campaigns. The calendar is the operational plan — it turns the strategic content matrix into dated, assigned, trackable publication slots.
Prerequisites
- Marketing project with content strategy defined
- Recommended: at least one campaign built
Output Formats
The calendar is maintained in two synchronized formats:
calendar/content-calendar.yaml— Machine-readable source of truthcalendar/content-calendar.md— Human-readable rendered view- CSV export (on request) — For import into HubSpot, Notion, Asana, etc.
Workflow
Step 1: Load Content Inventory
- Read
content-strategy.json— all planned content across markets and GTM paths - Read
campaigns/*.json— touchpoint timelines with day offsets - Scan
content/— identify what's generated (draft) vs. still planned - Read
marketing-project.json— cadence defaults
Step 2: Build Calendar
For each content piece, assign:
- Publication date: Based on campaign timeline or cadence defaults
- Channel: From content format → channel mapping
- Status: planned → drafted → reviewed → scheduled → published
- Owner: Marketing (default) or Sales (for enablement content)
- Dependencies: e.g., "LinkedIn promo post depends on blog being published"
Apply cadence rules from marketing-project.json:
- linkedin-post: 3x/week → Mon, Wed, Fri
- blog: 2x/month → 1st and 3rd Tuesday
- email-nurture: triggered by download (not scheduled)
- webinar: 1x/quarter → align with campaign timing
Step 3: Write Calendar Files
YAML source (content-calendar.yaml):
calendar:
start_date: "2026-04-01"
end_date: "2026-06-30"
entries:
- date: "2026-04-01"
day: "Mon"
market: "mid-market-saas-dach"
gtm_path: "ai-predictive-maintenance"
type: "demand-generation"
format: "linkedin-post"
title: "Trend hook: AI predictive maintenance"
file: "content/demand-generation/mid-market--ai-pred--linkedin-post-01.md"
channel: "linkedin"
status: "drafted"
campaign: "ai-pred-q2"
owner: "marketing"
notes: ""
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 · 126 lines · 84 tokens per session scan A 84eed664f862
content-calendar is a skill published in the GitHub repository cogni-work/insight-wave (13 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 1,222 once invoked, about $0.0004 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…