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 kostja94/marketing-skills --skill changeloggit clone --depth 1 https://github.com/kostja94/marketing-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/kostja94/marketing-skills/changelog)<a href="https://agentmods.dev/skills/kostja94/marketing-skills/changelog"><img src="https://agentmods.dev/badge/skills/kostja94/marketing-skills/changelog/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/kostja94/marketing-skills/changelog"><img src="https://agentmods.dev/badge/skills/kostja94/marketing-skills/changelog.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.00074 | $0.00662 |
| Opus 5 | $0.00037 | $0.00331 |
| Sonnet 5 | $0.00015 | $0.00132 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
changelog-page-generator 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- changelog-page-generator — 100% identical, 0 lines differ
- changelog-page-generator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pages: Changelog
Guides changelog and release notes pages. Typically at changelog.* subdomain or /changelog. Builds trust, reduces support, increases feature adoption.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for product and release cadence.
Identify:
- Product type: SaaS, API, mobile app, etc.
- Audience: End users, developers, both
- Release cadence: Weekly, monthly, continuous
- Format: Timeline, version-based, category (New, Improved, Fixed)
Changelog Structure
| Section | Purpose |
|---|---|
| Entry | Date, version, title |
| Category | New, Improved, Fixed, Deprecated (optional) |
| Description | What changed, why it matters |
| Link | To docs, blog, or in-app |
| Media | Screenshots, GIFs, videos (optional) |
Best Practices
Content
- User benefit first: "You can now X" not "We added X"
- Concrete: Specific features, not vague "improvements"
- Scannable: Headlines, bullets, tags
- Searchable: If many entries, add search/filter
Organization
- Reverse chronological: Newest first
- Grouping: By version or date range
- Tags: Feature area, product module (optional)
- RSS/email: Notify subscribers of updates
Placement
- Subdomain: changelog.yourdomain.com
- Path: /changelog, /updates, /releases
- Embed: Widget in app or docs sidebar
- Link from: Footer, docs, in-app
Output Format
- Structure (layout, entry format)
- Entry template (fields, tone)
- Navigation (filters, search)
- SEO (index, metadata)
- Integration (embed, RSS, email)
Related Skills
- docs-page-generator: Changelog linked from docs
- docs-page-generator: API changelog for developers; docs includes API Reference
- blog-page-generator: Major releases may have blog posts
- top-banner-generator: Announce major updates on main site
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 · 71 lines · 74 tokens per session scan A c4cf2a466377
changelog-page-generator is a skill published in the GitHub repository kostja94/marketing-skills (967 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 662 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-03.
Other skills, from other repositories
partner-affiliate
When the user wants to build a partner program, launch an affiliate program, design integration partnerships, or create distribution partnerships. Also use when the user mentions 'partnerships,' 'affiliate program,' 'referral program,' 'partner ecosystem,' 'integration partner,' 'reseller,' 'co-marketing,'…
kill-criteria-exit-ramps
Establishes pre-defined, objective conditions for stopping projects and specific decision points for continue/pivot/kill evaluations. Guides through defining kill criteria, setting go/no-go gates, avoiding sunk cost fallacy, and executing disciplined stopping decisions. Use when defining stopping rules for projects…
SEO Content Optimizer
Analyzes and rewrites content to maximize search engine visibility without sounding robotic.
review-resume
Comprehensive PM resume review and tailoring against 10 best practices including XYZ+S formula, keyword optimization, job-specific tailoring, and structure. Use when reviewing a PM resume, preparing for job applications, or improving resume impact.
forecast-discipline
Use to drive consistent forecast methodology, grading, and inspection cadences.
escalation-framework
Use to govern executive involvement, cross-functional response, and risk resolution for at-risk renewals.