Borrowing it
Nothing to install: this file belongs to Skowt/medusa. 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/Skowt/medusa/main/.claude/skills/medusa-commits-and-releases/SKILL.mdgit clone --depth 1 https://github.com/Skowt/medusaWrote 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/skowt/medusa/medusa-commits-and-releases)<a href="https://agentmods.dev/skills/skowt/medusa/medusa-commits-and-releases"><img src="https://agentmods.dev/badge/skills/skowt/medusa/medusa-commits-and-releases/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/skowt/medusa/medusa-commits-and-releases"><img src="https://agentmods.dev/badge/skills/skowt/medusa/medusa-commits-and-releases.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.00069 | $0.01376 |
| Opus 5 | $0.00034 | $0.00688 |
| Sonnet 5 | $0.00014 | $0.00275 |
| Haiku 4.5 | $0.00007 | $0.00138 |
Grade C, and why
medusa-commits-and-releases scanned grade C with 2 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 12d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
sh -c 'curl -fsSL https://raw.githubusercontent.com/Skowt/medusa/main/install.sh | sh' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
sh -c 'curl -fsSL https://raw.githubusercontent.com/Skowt/medusa/main/install.sh | sh' How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
medusa commits and releases
Commit format
Commit subjects follow a conventional-commit-lite convention. The .goreleaser.yml changelog filters depend on these prefixes to keep release notes focused on user-facing changes.
Subject line: <prefix>: <imperative summary> — ≤72 chars, lowercase after the prefix.
Allowed prefixes:
| Prefix | Meaning | Surfaces in release notes? |
|---|---|---|
feat: |
New user-facing feature | Yes |
fix: |
Bug fix | Yes |
refactor: |
Code restructuring, no behavior change | Yes |
perf: |
Performance improvement | Yes |
docs: |
Documentation only | No |
test: |
Tests only | No |
ci: |
CI/workflow/tooling | No |
chore: |
Routine maintenance, deps, housekeeping | No |
Optional PR reference at end of subject: (#123). GoReleaser carries it through to release notes; useful for linking context.
Body is optional. Include one when the why isn't obvious from the diff (hidden constraint, subtle invariant, reason for an unusual approach). Don't restate the what — the diff shows that.
Examples
fix: correct typo in copy gitignored files checkbox label
feat: add restart option to close tab dialog (#42)
refactor: extract PTY catch-up flush into dedicated helper
chore: bump tmux minimum version note
Anti-examples
Update stuff # no prefix, vague subject
feat: Added A Thing. # capitalized, period, past tense
Fix: bug in thing # wrong case, no detail
feat: massive overhaul of the state
machine plus some drive-by cleanups # multi-purpose commit, unclear scope
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.
- 12d ago First seen · 125 lines · 69 tokens per session scan C c805f826b326
medusa-commits-and-releases is a skill published in the GitHub repository Skowt/medusa (5 stars, last pushed 2d ago), licensed MIT. It adds 69 tokens to every session and 1,376 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
changelog
Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
git-workflow
Guides you through Git workflows — branching strategies, commit conventions, merge conflict resolution, and release management. Use when working with Git repositories or when the user asks about version control best practices.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.