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.
git clone --depth 1 https://github.com/SethCalkins/claude-ios-swift-pluginWrote 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/commands/sethcalkins/claude-ios-swift-plugin/app-changelog)<a href="https://agentmods.dev/commands/sethcalkins/claude-ios-swift-plugin/app-changelog"><img src="https://agentmods.dev/badge/commands/sethcalkins/claude-ios-swift-plugin/app-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/commands/sethcalkins/claude-ios-swift-plugin/app-changelog"><img src="https://agentmods.dev/badge/commands/sethcalkins/claude-ios-swift-plugin/app-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.00012 | $0.00672 |
| Opus 5 | $0.00006 | $0.00336 |
| Sonnet 5 | $0.00002 | $0.00134 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
app-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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store Changelog Generator
Generate user-facing App Store release notes from git history.
Instructions
1. Determine version range
-
Find the reference point:
- If argument provided, use that as the starting ref
- Otherwise, find the last git tag:
git describe --tags --abbrev=0 - If no tags, use the last 20 commits
-
Get current version:
- Check
Info.plistorPackage.swiftfor version number - Or use the branch name if it contains version info
- Check
2. Collect changes
-
Get commits since ref:
git log <from-ref>..HEAD --oneline --no-merges -
Get changed files:
git diff --name-only <from-ref>..HEAD -
Analyze commit messages for:
- Features (new functionality)
- Improvements (enhancements to existing features)
- Fixes (bug fixes)
- Performance (speed/memory improvements)
3. Filter for user-visible changes
Include:
- New features users can see or interact with
- Bug fixes that affected user experience
- Performance improvements users would notice
- UI/UX changes
Exclude:
- Internal refactoring
- Test additions/changes
- Documentation updates
- CI/CD changes
- Dependency updates (unless user-facing)
4. Generate release notes
-
Group by category:
- New Features
- Improvements
- Bug Fixes
- Performance
-
Write benefit-focused bullets:
- Focus on what users gain, not what code changed
- Use active voice: "Added", "Fixed", "Improved"
- Keep bullets concise (one line each)
- Avoid technical jargon
-
Validate each bullet maps to actual commits
5. Output
Provide two versions:
App Store Format (for What's New):
What's New in Version X.Y.Z
• Added dark mode support for all screens
• Fixed crash when loading large images
• Improved app launch time by 40%
• New widget for quick access to recent items
Detailed Format (for release notes):
## Version X.Y.Z
### New Features
- Dark mode support across all screens (#123)
- Home screen widget for recent items (#456)
### Improvements
- 40% faster app launch time (#789)
- Smoother scrolling in feed view (#101)
### Bug Fixes
- Fixed crash when loading large images (#112)
- Fixed login issue on iOS 18 (#131)
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 · 115 lines · 12 tokens per session scan A 59ed1078edde
app-changelog is a command published in the GitHub repository SethCalkins/claude-ios-swift-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 672 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 commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.