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 ScriptedAlchemy/agent-bundle --skill changesetsgit clone --depth 1 https://github.com/ScriptedAlchemy/agent-bundleWrote 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/scriptedalchemy/agent-bundle/changesets)<a href="https://agentmods.dev/skills/scriptedalchemy/agent-bundle/changesets"><img src="https://agentmods.dev/badge/skills/scriptedalchemy/agent-bundle/changesets.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.00044 | $0.00544 |
| Opus 5 | $0.00022 | $0.00272 |
| Sonnet 5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
changesets 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 3d 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.
This is a copy
100% identical to changesets — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Record what consumers need to know after implementation and focused validation.
Workflow
- Inspect the complete diff and identify directly affected published packages.
- Classify impact across source types, runtime behavior, entrypoints, required services, lifecycle, and persisted or wire data.
- Perform the breaking audit below.
- Record either a reason no changeset is required or one coherent changeset. When required, read authoring.md.
- Validate package names, frontmatter, bump policy, and consumer-facing text.
Do not include unrelated worktree changes.
Requirement
Create a changeset for observable runtime behavior changes, including bug fixes; exported value or public type changes; entrypoint or export-map changes; changes to required services, errors, ownership, defaults, or lifecycle; and persisted, serialization, protocol, or wire-format changes.
Tests-only changes, behavior-preserving internal refactors, documentation or JSDoc maintenance, and unpublished tooling normally do not need one. When unclear, inspect exports and consumer-visible declarations rather than inferring from source location.
Breaking Audit
A change is breaking when valid existing consumer code, configuration, or data must change to keep compiling or behaving according to the previous contract. Audit every surface:
- Names and locations: exports, entrypoints, compatibility exports, and module paths.
- Call compatibility: parameters, accepted inputs, overload resolution, generic parameters, and defaults.
- Result compatibility: return and error types, output narrowing, members, inference, and required services.
- Runtime contracts: defaults, failures, interruption, concurrency, ordering, resource lifetime, acquisition, cleanup, and mutation.
- Data compatibility: persisted schemas, encodings, database layouts, protocols, and wire formats.
Additive exports, optional parameters, and behavior-preserving implementations are normally non-breaking. A fix restoring the documented contract is normally non-breaking but still needs a changeset when its operational impact is consumer-visible. Verify representative existing calls when overload ordering, structural assignability, or inference makes compatibility uncertain. API diff output is mechanical evidence, not a semantic-version decision.
What ships with it
1 file 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.
- 3d ago First seen · 59 lines · 44 tokens per session scan A 285aa88c9322
changesets is a skill published in the GitHub repository ScriptedAlchemy/agent-bundle (9 stars, last pushed today), licensed Apache-2.0. It adds 44 tokens to every session and 544 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to changesets, differing in 0 lines, and is treated as a copy.
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.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
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.