Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mattppal/shipping-sznnpx agentmods add skills/mattppal/shipping-szn/changelog-formattingWrote 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/mattppal/shipping-szn/changelog-formatting)<a href="https://agentmods.dev/skills/mattppal/shipping-szn/changelog-formatting"><img src="https://agentmods.dev/badge/skills/mattppal/shipping-szn/changelog-formatting/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/mattppal/shipping-szn/changelog-formatting"><img src="https://agentmods.dev/badge/skills/mattppal/shipping-szn/changelog-formatting.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.01763 |
| Opus 5.5 | $0.00016 | $0.00705 |
| Sonnet 5.5 | $0.00008 | $0.00353 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
changelog-formatting 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 2mo 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Formatting Skill
This skill helps you format changelog content according to Replit's template structure.
Overview
Convert raw changelog content into properly structured documentation following:
- Correct frontmatter with date and metadata
- Proper section organization ("What's new" TOC, then "Platform" and "Teams and Enterprise" sections)
- Correct media path formatting and Frame wrappers
- Consistent formatting and style
- No Slack links in final output (remove all Slack announcement links)
Quick Start
1. Add Frontmatter
Use the add_changelog_frontmatter tool - don't write frontmatter manually:
# The tool will create:
---
title: October 30, 2025
description: 2 min read
---
2. Create "What's new" TOC
Immediately after frontmatter, add a "## What's new" section with anchor-linked bullet points for ALL updates (both Platform and Teams/Enterprise):
## What's new
* [Feature One](#feature-one)
* [Feature Two](#feature-two)
* [Enterprise Feature](#enterprise-feature)
Anchor format: Convert feature name to lowercase, replace spaces with hyphens.
3. Categorize Updates into Sections
After the TOC, organize content into two main sections:
- ## Platform: General features, tools, improvements
- ## Teams and Enterprise: SSO, SAML, SCIM, Identity, Access Management, Viewer Seats, Groups, Permissions
4. Structure Content
Each section should have ### subsections for each feature:
## Platform
### Feature One
Description of the feature.
### Feature Two
Description of the feature.
## Teams and Enterprise
### Enterprise Feature
Description of the feature.
5. Format Media (CRITICAL)
Process for each media reference:
-
Verify the file exists first:
- Check if
./docs/updates/media/YYYY-MM-DD/filenameexists on the filesystem - If the file doesn't exist, REMOVE the reference from the markdown
- Only process media that actually exists
- Check if
-
Convert local paths to public CDN paths:
./media/YYYY-MM-DD/filename → /images/changelog/YYYY-MM-DD/filename
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2mo ago First seen · 258 lines · 41 tokens per session scan A b13811523d92
changelog-formatting is a skill published in the GitHub repository mattppal/shipping-szn (2 stars, last pushed 8mo ago), licensed MIT. It adds 41 tokens to every session and 1,763 once invoked, about $0.0002 per session on Opus 5.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-08-31.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.