Borrowing it
Nothing to install: this file belongs to fagemx/prismstack. 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/fagemx/prismstack/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/fagemx/prismstackWrote 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/fagemx/prismstack/release)<a href="https://agentmods.dev/skills/fagemx/prismstack/release"><img src="https://agentmods.dev/badge/skills/fagemx/prismstack/release/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/fagemx/prismstack/release"><img src="https://agentmods.dev/badge/skills/fagemx/prismstack/release.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.00057 | $0.00763 |
| Opus 5.5 | $0.00023 | $0.00305 |
| Sonnet 5.5 | $0.00011 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade B, and why
release scanned grade B with 1 finding 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 2mo 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
ls ~/.claude/skills/prismstack/ How it starts
The opening of the file, as written. The whole thing — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release: Ship a New Prismstack Version
You are the release manager. You ensure every release is tested, documented, tagged, and installed.
Phase 1: Pre-Flight Checks
Run tests
bash test/install-test.sh
All tests must pass (expect 67/67). If any fail, stop and report: "Cannot release — N test failures. Fix first."
Check working tree
git status --short
Must be clean (no uncommitted changes). If dirty, stop and report: "Cannot release — uncommitted changes found. Commit or stash first."
Review changes since last release
git describe --tags --abbrev=0 2>/dev/null || echo "no-tags"
Then show commits since that tag:
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD~20")..HEAD
Summarize the changes by category: features, fixes, docs, refactors.
Phase 2: Determine Version Bump
Read the current version:
cat VERSION
Read CHANGELOG.md for any unreleased section.
Apply semantic versioning:
- breaking: changes → major bump (0.5.0 → 1.0.0)
- feat: changes → minor bump (0.5.0 → 0.6.0)
- fix: only → patch bump (0.5.0 → 0.5.1)
Present the proposed version and changelog to the user. Ask for confirmation before proceeding:
"Proposed release: vX.Y.Z with these changes: [summary]. Proceed?"
Do NOT continue without user confirmation.
Phase 3: Update Files
VERSION file
Write the new version string (just the number, no v prefix).
CHANGELOG.md
Add a new version header at the top of the changelog (below any title):
## [X.Y.Z] - YYYY-MM-DD
### Added
- feat: description (from commit messages)
### Fixed
- fix: description
### Changed
- refactor: description
Organize commits under the appropriate heading. Drop trivial commits (typo fixes, etc.) unless they are the only changes.
Phase 4: Commit and Tag
git add VERSION CHANGELOG.md
git commit -m "chore: release vX.Y.Z"
git tag vX.Y.Z
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.
- 2mo ago First seen · 131 lines · 57 tokens per session scan B fc590834c58e
release is a skill published in the GitHub repository fagemx/prismstack (1 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 763 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
cdd-close
Independent cdd-close orchestrator -- Node-anchored flow with digraph as single control-flow source of truth. Consumes the /superpowers:finishing-a-development-branch（pi：/skill:finishing-a-development-branch） flow inline as this session's baseline for the finish decision, gates on the finish outcome, then closes…
changelog-generator
Generate changelogs from git commits. Use when user says "generate changelog", "update changelog", "what changed since last release", or before preparing a new release.
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
om-auto-continue-pr-loop
Advanced om-auto-continue-pr for PRs started by om-auto-create-pr-loop — claims the PR, resumes from the first non-done PLAN.md Tasks row in an isolated worktree, keeps the per-step commit and checkpoint discipline (integration tests + screenshots for UI), runs the full gate at completion, keeps spec-only design PRs…
om-auto-update-changelog
Draft a CHANGELOG.md release entry in an emoji-driven format for every PR merged since the last release, then delegate to om-auto-create-pr so it lands as a docs PR against the configured base branch. Honors the Supersede Credit Rule and verifies every credit against commit authorship, so carry-forwards and umbrella…
utility-pm-release-conductor
Walk the guided 6-gate release runbook (G0 readiness, G1 adversarial review, G2 version bump and CHANGELOG, G2.5 commit and re-verify, G3 tag and push, G4 post-tag hygiene) via the pm-release-conductor sub-agent. Refuses gate bypasses and tags only the re-verified SHA. Use when cutting a pm-skills release.