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 cenconq25/claude-code-app-studio --skill changeloggit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/changelog)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/changelog"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/changelog.svg" alt="Measured on agentmods" 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.00043 | $0.01761 |
| Opus 5 | $0.00022 | $0.00881 |
| Sonnet 5 | $0.00009 | $0.00352 |
| Haiku 4.5 | $0.00004 | $0.00176 |
Grade A, and why
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 4d 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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog
Translate a git history window plus the corresponding sprint and PRD context into a clean changelog. The internal version explains what shipped and why; the user-facing version is short, plain, and respectful of store character limits.
Phase 1: Resolve the Window
Parse arguments:
--from=<tag-or-date>and--to=<tag-or-date>define the explicit window.--version=<v>looks up the previous release tag and uses it as the--from.- Default:
--from= previous release tag,--to= HEAD.
Use Bash:
git tag --sort=-creatordate | head -n 5
git log --pretty=format:'%h%x09%s%x09%an' [from]..[to]
Capture commits, authors, and SHAs.
Phase 2: Pull Auxiliary Context
Read in parallel:
- Sprint files closed within the window:
production/sprints/sprint-*.md. - Story files closed within the window:
production/epics/**/story-*.mdfiltered byStatus: CompleteandClosed: [in-window]. - Bug records closed within the window:
production/qa/bugs/BUG-*.mdfiltered byStatus: Closedand a closing date in window. - PRD updates in the window via
git log -- design/prd/. - ADRs accepted in the window via
git log -- docs/architecture/.
Phase 3: Categorize Commits
Run each commit through a classifier:
- Features — commit message includes "feat" / "feature" / refers to a story closing as new functionality.
- Improvements — "perf", "improve", "polish", "tune".
- Fixes — "fix", "bug", references a BUG ID.
- Security — "security", "CVE", references a security audit finding.
- Internal — "refactor", "chore", "test", "ci", "docs", "style".
- Reverted —
Revert "..."style messages.
For each commit, attempt to enrich:
- Linked story (commit body or branch name often contains
STORY-NN). - Linked bug (BUG-NN).
- Linked PRD section.
Phase 4: Internal Changelog
Render at one entry per change. Structure:
# Internal Changelog — [version]
Window: [from] -> [to]
Author count: [N]
Commit count: [N]
## Features
- [STORY-NN] [headline] — [PRD ref] (commits: abc123, def456)
Notes: [summary, framework notes, ADR ref]
## Improvements
- [headline] — [perf-profile reference if perf-related]
## Fixes
- [BUG-NN] [headline] (commits: ...)
## Security
- [security-audit ref] [summary]
## Internal / Refactors
- [headline]
## Reverted
- [reverted commit + reason if known]
## Notes for Engineers
- API changes: [list]
- Migration steps: [list]
- Deprecations introduced: [list]
- New ADRs: [IDs]
## Stats
- Stories closed: [N]
- Bugs closed: [N]
- Test files added: [N]
- LOC delta: [+P / -Q]
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.
- 4d ago First seen · 252 lines · 43 tokens per session scan A 4d8b10696675
changelog is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 43 tokens to every session and 1,761 once invoked, about $0.0002 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
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
git-push
A GitHub publishing workflow that handles first-time uploads, routine updates, and tagged releases. Git is a system for recording code changes, while GitHub hosts repositories and releases online.