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 vishalvshekkar/app-store-toolkit --skill changeloggit clone --depth 1 https://github.com/vishalvshekkar/app-store-toolkitWrote 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/vishalvshekkar/app-store-toolkit/changelog)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/changelog"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/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/vishalvshekkar/app-store-toolkit/changelog"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/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.00017 | $0.00962 |
| Opus 5 | $0.00009 | $0.00481 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00002 | $0.00096 |
Grade A, and why
app-store-toolkit: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 10d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-store-toolkit:changelog
You are generating release notes (What's New) for an app version.
Steps
1. Load Configuration
Call store_read_config to get voice/tone settings and platforms.
If no config exists, tell the user: "Run /app-store-toolkit:setup first to configure your app." and STOP.
2. Determine Version Range
Follow this priority order:
Priority 1 — User specified range in $ARGUMENTS:
If the user provided a range like v1.0..v2.0 or 1.0..2.0, use that directly.
Priority 2 — Git tags:
Run git tag --sort=-version:refname to list tags. Take the latest two tags as the range.
- If only one tag exists, use
{tag}..HEAD - If no tags exist, fall through to Priority 3
Priority 3 — Existing release notes:
Call store_list with type: "release_notes" to check for existing versions.
If found, the latest version is the "from" — ask the user for the new version number.
Priority 4 — Manual: Ask the user for:
- The version number (e.g., "2.1.0")
- What changed (they can describe changes in natural language)
3. Gather Changes
Git mode (Priorities 1-2):
Run git log {from}..{to} --oneline --no-decorate to get the commit list.
Parse conventional commits if enabled in config:
feat:/feature:→ Features / Newfix:/bugfix:→ Bug Fixesperf:→ Performancerefactor:/chore:/docs:/style:/test:/ci:/build:→ Improvements (or skip if minor)
For non-conventional commits, use AI to categorize them.
Manual mode (Priorities 3-4): Use whatever the user described as the source material.
4. Generate Release Notes
Create user-friendly release notes following these rules:
- Apply configured voice/tone
- Maximum 4000 characters
- Focus on user-visible changes (skip internal refactors, CI changes, dependency bumps unless significant)
- Group by category (New, Improved, Fixed) when there are many changes
- For small releases, a simple paragraph or bullet list works
- Start with the most impactful change
- Use language users understand (not developer jargon)
- Be specific about what changed, not vague ("Fixed a bug where photos failed to upload on slow connections" not "Bug fixes")
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.
- 10d ago First seen · 114 lines · 17 tokens per session scan A d280942081a0
app-store-toolkit:changelog is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 962 once invoked, about $0.0001 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-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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
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.
updater_guide
Guidance for checking for and installing Row-Bot updates.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.