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/asasugar/superspec/changeset-releasenpx skills add asasugar/SuperSpec --skill changeset-releasegit clone --depth 1 https://github.com/asasugar/SuperSpecWrote 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/asasugar/superspec/changeset-release)<a href="https://agentmods.dev/skills/asasugar/superspec/changeset-release"><img src="https://agentmods.dev/badge/skills/asasugar/superspec/changeset-release.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 | $0.00091 | $0.00953 |
| Opus 5 | $0.00046 | $0.00477 |
| Sonnet 5 | $0.00018 | $0.00191 |
| Haiku 4.5 | $0.00009 | $0.00095 |
Grade A, and why
changeset-release 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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changeset Release
Manage the full release lifecycle for this pnpm monorepo using @changesets/cli.
Project Context
- Monorepo root: project root with
pnpm-workspace.yaml - Package manager: pnpm
- Packages:
packages/cli→@superspec/cli - Changeset config:
.changeset/config.json(access: public, baseBranch: master) - NPM auth: user-level
~/.npmrcwith token
Commands Reference
| Action | Command |
|---|---|
| Create changeset | pnpm changeset |
| Bump versions | pnpm changeset:version |
| Build + Publish | pnpm release |
Workflows
1. Create Changeset
Create a .changeset/*.md file describing the change.
pnpm changeset
This is interactive. When automating, create the file directly:
# Generate a random changeset filename
CHANGESET_ID=$(node -e "console.log(Math.random().toString(36).slice(2,10))")
cat > .changeset/${CHANGESET_ID}.md << 'EOF'
---
"@superspec/cli": patch
---
<changeset summary here>
EOF
Bump type selection:
- patch: bug fixes, minor tweaks
- minor: new features, non-breaking changes
- major: breaking changes
2. Check Pending Changesets
List all pending changeset files (excluding config.json and README.md):
ls .changeset/*.md 2>/dev/null | grep -v README.md
If no files found → nothing pending, no version bump needed.
To view content:
for f in .changeset/*.md; do
[[ "$(basename "$f")" == "README.md" ]] && continue
echo "=== $f ==="
cat "$f"
echo
done
3. Version Bump
Consume pending changesets and update package versions + CHANGELOG:
pnpm changeset:version
This will:
- Read all pending
.changeset/*.mdfiles - Update
package.jsonversion fields - Update/create
CHANGELOG.mdin each affected package - Delete consumed changeset files
After version bump, review changes:
git diff packages/*/package.json packages/*/CHANGELOG.md
4. Publish to npm
Build all packages and publish to npm registry:
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 · 139 lines · 91 tokens per session scan A 672d60f23eef
changeset-release is a skill published in the GitHub repository asasugar/SuperSpec (15 stars, last pushed 5mo ago), licensed MIT. It adds 91 tokens to every session and 953 once invoked, about $0.0005 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-30.
Other skills, from other repositories
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup.
comet-release
根据真实版本和分支范围准备 Comet 发布或发布说明更新，保持 Changelog 面向用户、双语网站文档一致、生成资产已验证，并明确 Git 交付边界。Beta、hotfix、版本检查、发布说明或发布就绪检查时使用。.
comet-safe-delivery
在保护无关脏改动、关联 worktree、子模块和用户明确边界的前提下，提交、推送、合并或完成范围明确的 Comet 变更。用户要求提交、推送、合并回目标分支、清理 worktree 或交付已准备好的改动时使用。.
release
Cut a prospec GitHub release — bump version strings, tag, and publish release notes in the established format so the Release Binaries workflow attaches multi-platform binaries. Triggers: release, publish release, cut a release, ship a version, 發布, 發佈, 出版本, 發版, 版本發布, 發布 release.
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.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.