Borrowing it
Nothing to install: this file belongs to tyler-mitchell/type-atlas. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tyler-mitchell/type-atlas/main/.skills/add-change/SKILL.mdgit clone --depth 1 https://github.com/tyler-mitchell/type-atlasWrote 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/tyler-mitchell/type-atlas/add-change)<a href="https://agentmods.dev/skills/tyler-mitchell/type-atlas/add-change"><img src="https://agentmods.dev/badge/skills/tyler-mitchell/type-atlas/add-change/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/tyler-mitchell/type-atlas/add-change"><img src="https://agentmods.dev/badge/skills/tyler-mitchell/type-atlas/add-change.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.00046 | $0.01233 |
| Opus 5.5 | $0.00018 | $0.00493 |
| Sonnet 5.5 | $0.00009 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00123 |
Grade A, and why
add-change 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 1mo 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
94% identical to add-change — 3 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a bumpy bump file
You are helping the user create a bumpy bump file — a markdown file in .bumpy/ that describes which packages changed and how. Bumpy uses these to bump versions and generate changelogs.
Steps
1. Gather context
First, understand what changed. Run these in parallel:
git diff --stat— see which files changedgit diff --cached --stat— see staged changesbumpy status --json— see if there are already pending bump files
If the user provided a description via $ARGUMENTS, use that as additional context for understanding the change.
Review the diff output to understand the scope of changes.
2. Identify affected packages
Determine which workspace packages are affected by the changes. Map changed files to their packages based on directory structure.
If unsure which packages exist, run:
bumpy status --packages 2>/dev/null || cat package.json
3. Determine bump levels
For each affected package, choose the appropriate bump level:
| Level | When to use |
|---|---|
| major | Breaking changes: removed/renamed exports, changed function signatures, dropped support |
| minor | New features: added exports, new options, new functionality |
| patch | Bug fixes, internal refactors, documentation, dependency updates |
Use none in a bump file to acknowledge a change without triggering a direct bump. Cascading bumps from other packages can still apply normally.
4. Write a clear summary
Write a concise summary for the CHANGELOG entry. Keep it short — ideally a single sentence, at most two. Good summaries:
- Start with a verb: "Added...", "Fixed...", "Refactored..."
- Focus on user-facing impact, not implementation details
- Are specific enough to be useful months later
- Avoid filler, jargon, or restating the bump level
- Don't list every file changed — describe the logical change
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.
- 1mo ago First seen · 130 lines · 46 tokens per session scan A dafa6c727bb3
add-change is a skill published in the GitHub repository tyler-mitchell/type-atlas (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 1,233 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to add-change, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). The work commits land first, then the version bump, verification, and the release commit on top. Stops at "committed locally on main" — or, when the project releases…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
release-and-publish
Ship a release end-to-end across every registry this project targets (npm, MCP Registry). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already complete — this skill is the post-wrapup…
studio-source-control
Drive a scoped application's linked git repository from the instance — what has to be true before Source Control works at all, the commit-then-push order, stashes and branches over /api/snsourcecontrol, and when this replaces update sets rather than sitting next to them.