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 HoangNguyen0403/agent-skills-standard --skill common-store-changeloggit clone --depth 1 https://github.com/HoangNguyen0403/agent-skills-standardWrote 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/hoangnguyen0403/agent-skills-standard/common-store-changelog)<a href="https://agentmods.dev/skills/hoangnguyen0403/agent-skills-standard/common-store-changelog"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-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/hoangnguyen0403/agent-skills-standard/common-store-changelog"><img src="https://agentmods.dev/badge/skills/hoangnguyen0403/agent-skills-standard/common-store-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.00060 | $0.00805 |
| Opus 5.5 | $0.00024 | $0.00322 |
| Sonnet 5.5 | $0.00012 | $0.00161 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
common-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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Store Changelog Standard
Priority: P1 (HIGH)
Always-Apply Rules
- Character limits: App Store ≤ 4000 chars. Google Play ≤ 500 chars — validate before output.
- Benefit language: Write what user gains, not what code changed. "Faster checkout" not "refactored cart service".
- Bullet-only format: One sentence per bullet. No paragraphs. No headers inside notes.
- Drop internal commits: Exclude
chore,refactor,ci,build,test, dependency bumps, and config changes — no user impact. - Suppress internal SDK changes: Never mention an analytics or other internal SDK update in store notes; omit it silently rather than explaining the omission.
- Deduplicate: Merge commits touching same feature into one bullet.
Workflow
- Collect: Run
git log <last-tag>..HEAD --oneline(or use provided commit list). If no tag exists, use full history. - Triage: Scan commits and touched files. Group by theme:
New,Improved,Fixed. Drop internal-only. - Draft — App Store: Write 5–10 benefit-focused bullets, including user-facing changes such as onboarding when present. Optional
What's New in [Version]header. - Draft — Google Play: Compress App Store draft to ≤ 500 chars. Prioritise top 3–5 user-facing changes.
- Validate: Count characters per store. Check every bullet maps to real commit. Remove jargon.
See Commit-to-Bullet Examples for mapping patterns.
Output Format
App Store (≤ 4000 chars):
What's New in Version X.Y
• [New] <user benefit — one sentence>
• [Improved] <user benefit — one sentence>
• [Fixed] <user benefit — one sentence>
Google Play (≤ 500 chars):
• <highest-impact change>
• <second change>
• <third change>
[Bug fixes and performance improvements.]
Anti-Patterns
- No jargon: Never use
refactor,migrated,deprecated,PR,hotfix, or internal ticket IDs. - No chore bullets:
chore: upgrade Gradle→ drop entirely, never paraphrase as user feature. - No bundled bullets: "Fixed login and improved search and added dark mode" → three separate bullets.
- No character overrun: Validate Play Store notes ≤ 500 chars before returning — truncate + rewrite if needed.
- Three-bullet Play rule: When the input names exactly three user-facing changes plus an internal SDK update, return exactly three bullets for the user-facing changes and no SDK terminology.
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.
- 1mo ago First seen · 81 lines · 60 tokens per session scan A 296c7e1dbd77
common-store-changelog is a skill published in the GitHub repository HoangNguyen0403/agent-skills-standard (583 stars, last pushed today), licensed MIT. It adds 60 tokens to every session and 805 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-30.
Other skills, from other repositories
mobile-web-app
Add router-agnostic, native app-like page transitions to mobile web apps with SSGOI. Explore live drill, sheet, slide, and zoom demos at https://ssgoi.dev. Use when building or improving a mobile web app's routed page structure, layouts, or transitions, or when a project uses SSGOI or an @ssgoi package.
flutter-idioms
Flutter idioms: Riverpod 3 state management, Freezed immutable models, gorouter navigation, const widget optimization, and repository patterns. Use when developing, refactoring, or reviewing Flutter mobile applications.
nextjs-idioms
Next.js App Router architecture: React Server Components (RSC), Server Actions, nested layouts, route handlers, and streaming. Use when building or refactoring Next.js web applications. Pair with react-idioms and typescript-idioms.
react-idioms
React 19+ patterns: custom hooks, Suspense boundaries, state management, component composition, and web performance. Use when developing or refactoring React components and client applications. Pair with typescript-idioms.
mobile-testing
Mobile E2E testing patterns — Flutter integrationtest, Patrol, Maestro, golden testing, device matrix, and test data management. Use when writing E2E tests for mobile applications.
swift-idioms
Swift idioms and best practices: value types, Optionals hygiene, protocol-oriented design, async/await and Actor concurrency, and XCTest. Use when writing, refactoring, or reviewing Swift iOS, macOS, or server-side code.