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 patrickserrano/lacquer --skill release-app-store-changeloggit clone --depth 1 https://github.com/patrickserrano/lacquerWrote 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/patrickserrano/lacquer/release-app-store-changelog)<a href="https://agentmods.dev/skills/patrickserrano/lacquer/release-app-store-changelog"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/release-app-store-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/patrickserrano/lacquer/release-app-store-changelog"><img src="https://agentmods.dev/badge/skills/patrickserrano/lacquer/release-app-store-changelog.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.00042 | $0.00816 |
| Opus 5.5 | $0.00017 | $0.00326 |
| Sonnet 5.5 | $0.00008 | $0.00163 |
| Haiku 4.5 | $0.00004 | $0.00082 |
Grade A, and why
release-app-store-changelog 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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store Changelog
Overview
Generate comprehensive, user-facing changelog from git history since the last tag, then translate commits into clear App Store release notes.
Workflow
1) Collect Changes
Get commits since the last tag:
# Find the last tag
git describe --tags --abbrev=0
# List commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --oneline
# Or with more detail
git log $(git describe --tags --abbrev=0)..HEAD --pretty=format:"%h %s" --no-merges
If comparing specific refs:
git log v1.2.3..HEAD --oneline --no-merges
If no tags exist:
git log --oneline --no-merges -50 # Last 50 commits
2) Triage for User Impact
Scan commits and identify user-visible changes:
Include:
- New features
- UI changes
- Behavior changes
- Bug fixes users would notice
- Performance improvements with visible impact
Exclude:
- Refactors
- Dependency bumps
- CI changes
- Developer tooling
- Internal logging
- Analytics changes (unless affecting user privacy/behavior)
Group changes by theme:
- New: New features and capabilities
- Improved: Enhancements to existing features
- Fixed: Bug fixes
3) Draft App Store Notes
Write short, benefit-focused bullets:
- Use clear verbs and plain language
- Avoid internal jargon, ticket IDs, file paths
- Prefer 5-10 bullets unless user specifies different length
- Each bullet: one sentence, starts with a verb
Language guidance:
- Translate technical terms to user-facing descriptions
- Avoid: "API", "refactor", "nil", "crash log", "dependency"
- Use: "Improved", "Added", "Fixed", "Updated"
- Keep tense consistent (present or past)
Examples:
- "Added account switching from the profile menu."
- "Improved timeline loading speed on slow connections."
- "Fixed media attachments not opening in full screen."
4) Validate
- Every bullet maps to a real change in the range
- No duplicate bullets describing the same change
- No internal jargon or file paths
- Final list fits App Store text limits (if provided)
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.
- 1mo ago First seen · 139 lines · 42 tokens per session scan A 6dfc43a6771f
release-app-store-changelog is a skill published in the GitHub repository patrickserrano/lacquer (4 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 816 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-09-03.
Other skills, from other repositories
release
Prepare code for release (version bumps, changelog, README updates) and create an annotated tag to trigger the GoReleaser workflow.
tools-checkout
Fetch the internal tools repository at a pinned release.
hotfix-branch
Prepares a hotfix on a branch cut from the latest release tag. Use when a production bug needs a patch release.
python-format
Formats Python files with ruff format and reports which files changed.
release-notes
Drafts release notes from merged PRs and posts them to the #releases Slack channel.
ReleaseNotes
Drafts release notes from merged pull requests. Use when a release is being prepared.