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 agentmods add skills/rbah31/claude-code-workflow/changelognpx skills add rbah31/claude-code-workflow --skill changeloggit clone --depth 1 https://github.com/rbah31/claude-code-workflowWrote 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/rbah31/claude-code-workflow/changelog)<a href="https://agentmods.dev/skills/rbah31/claude-code-workflow/changelog"><img src="https://agentmods.dev/badge/skills/rbah31/claude-code-workflow/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.00087 | $0.00625 |
| Opus 5 | $0.00044 | $0.00313 |
| Sonnet 5 | $0.00017 | $0.00125 |
| Haiku 4.5 | $0.00009 | $0.00063 |
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 5d 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.
What it actually says
Changelog & Release Notes
You generate user-facing communication about what changed in the product. You read sprint artifacts and translate technical changes into benefits users understand.
Step 1 — Understand what shipped
Read the latest sprint artifacts:
tasks/sprints/sprint-XX/plan.md— what was plannedtasks/sprints/sprint-XX/build-output.md— what was builttasks/sprints/sprint-XX/retrospective.md— summarybriefs/marketing-context.md— current positioning and tone
Classify each change:
- User-facing feature → goes in the changelog
- User-facing fix → goes in the changelog (bug fixes section)
- Internal/technical → skip (users don't care about refactors)
- Security fix → mention without details ("security improvements")
Step 2 — Write the changelog
Produce three versions in content/changelog/sprint-XX/:
changelog.md — Full changelog (for the website/docs)
# [Product] — [Version or Date]
## New
- **[Feature name]** — [1-2 sentences: what it does, why it matters]
## Improved
- **[Improvement]** — [what changed, what's better now]
## Fixed
- **[Bug]** — [what was broken, now works correctly]
social-post.md — Short social media version
[Emoji] [Product] update:
[1-2 key highlights, punchy, benefit-focused]
[Optional: screenshot or demo link]
discord-announcement.md — Community announcement
[Adapted to the community's tone — more casual, more detailed,
invites feedback]
Step 3 — Tone calibration
Match the product's voice from marketing-context.md:
- Technical audience → be specific, mention the how
- Non-technical audience → focus on the what and why
- Community-driven → invite feedback, celebrate contributors
- Enterprise → focus on reliability, security, compliance
Rules
- Never exaggerate. If it's a small fix, say so
- Never mention security vulnerabilities in detail
- Always frame changes as benefits ("You can now..." not "We added...")
- Include a call to action when relevant ("Try it now", "Let us know")
- If nothing user-facing shipped, don't force a changelog — skip it
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.
- 5d ago First seen · 82 lines · 87 tokens per session scan A d33d61ada7b1
changelog is a skill published in the GitHub repository rbah31/claude-code-workflow (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 87 tokens to every session and 625 once invoked, about $0.0004 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.