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 CodePhobiia/claude-roblox-game-studio --skill changeloggit clone --depth 1 https://github.com/CodePhobiia/claude-roblox-game-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/codephobiia/claude-roblox-game-studio/changelog)<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/changelog"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/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/codephobiia/claude-roblox-game-studio/changelog"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/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.00018 | $0.00573 |
| Opus 5 | $0.00009 | $0.00287 |
| Sonnet 5 | $0.00004 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
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 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/changelog — Generate Changelog
Delegate to: release-manager (with writer for language polish)
Steps
1. Determine Range
Ask: "What range?" Options:
- Since last release (tag or branch)
- Since last commit of type N
- Custom date range
- Custom commit range
Default: since the last tag matching v*.
2. Gather Git History
# Get commits since last tag
git log $(git describe --tags --abbrev=0)..HEAD --format="%H %s"
# Or date range
git log --since="2 weeks ago" --format="%H %s"
3. Categorize Commits
Parse conventional commit format (type(scope): description):
- feat: New features
- fix: Bug fixes
- perf: Performance improvements
- refactor: Code refactoring
- docs: Documentation
- test: Tests
- chore: Maintenance
- style: Formatting
Group commits by type.
4. Extract Design Doc Changes
Cross-reference with design docs that were updated:
git diff --name-only $(git describe --tags --abbrev=0)..HEAD -- design/
Note any GDDs that changed — those probably correspond to feature work.
5. Generate Two Outputs
Technical Changelog (for team / docs)
# Changelog
## [Unreleased]
### Added
- combat: Add dodge mechanic (#42)
- shop: Add GamePass: VIP Membership (#43)
### Changed
- combat: Rebalance weapon damage curves (#44)
### Fixed
- datastore: Fix race condition in save logic (#45)
- ui: Fix shop button alignment on mobile portrait (#46)
### Performance
- combat: Reduce hit detection overhead by 40% (#47)
### Deprecated
- (none)
### Removed
- (none)
### Security
- remotes: Add rate limiting to purchase remote (#48)
Player-Facing Patch Notes
(Handoff to /patch-notes for this — changelog is technical)
6. Output
Present the technical changelog. On approval, write to CHANGELOG.md (or append to existing).
If the project has no CHANGELOG.md, offer to create one using Keep a Changelog format.
Changelog Style
- Use past tense ("Added" not "Adds")
- One line per change
- Include issue/PR references
- Group related small changes
- Lead with user-facing impact, not implementation details
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 · 96 lines · 18 tokens per session scan A 9d84a80d80d7
changelog is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 573 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.