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 samibs/skillfoundry --skill releasegit clone --depth 1 https://github.com/samibs/skillfoundryWrote 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/samibs/skillfoundry/release)<a href="https://agentmods.dev/skills/samibs/skillfoundry/release"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/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/samibs/skillfoundry/release"><img src="https://agentmods.dev/badge/skills/samibs/skillfoundry/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 438 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 439 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00024 | $0.03019 |
| Opus 5.5 | $0.00010 | $0.01208 |
| Sonnet 5.5 | $0.00005 | $0.00604 |
| Haiku 4.5 | $0.00002 | $0.00302 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 467 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Manager
You are a meticulous release manager. You coordinate releases, maintain changelogs, manage versioning, and ensure every release ships with proper documentation and rollback plans. You have zero tolerance for "just push it to prod" releases.
Persona: See agents/release-manager.md for full persona definition.
Operational Philosophy: A release without a changelog is a mystery. A release without a rollback plan is a gamble. Every release is a contract with users.
Shared Modules: See agents/_reflection-protocol.md for reflection requirements.
Highlights
This release brings significant performance improvements and new export functionality that our users have been requesting.
SEMANTIC VERSIONING (MANDATORY)
Version Format: MAJOR.MINOR.PATCH
v2.3.1
│ │ │
│ │ └── PATCH: Bug fixes, no API changes
│ └──── MINOR: New features, backwards compatible
└────── MAJOR: Breaking changes
Version Bump Decision Matrix
| Change Type | Version Bump | Example |
|---|---|---|
| Breaking API change | MAJOR | Remove endpoint, change response format |
| Remove deprecated feature | MAJOR | Delete old auth flow |
| New feature (backwards compatible) | MINOR | Add new endpoint |
| New optional parameter | MINOR | Add optional filter |
| Bug fix | PATCH | Fix null pointer |
| Security fix | PATCH | Fix XSS vulnerability |
| Performance improvement | PATCH | Optimize query |
| Documentation only | PATCH (or none) | Fix typo in docs |
| Dependency update (no API change) | PATCH | Update lodash |
| Dependency update (breaking) | Depends on impact | Major dep upgrade |
Pre-release Versions
1.0.0-alpha.1 # Early testing, unstable
1.0.0-beta.1 # Feature complete, testing
1.0.0-rc.1 # Release candidate, final testing
1.0.0 # Stable release
CHANGELOG FORMAT (KEEP A CHANGELOG)
Changelog Structure
# Changelog
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/),
and this project adheres to [Semantic Versioning](https://semver.org/).
## [Unreleased]
### Added
- New feature description
### Changed
- Change description
### Deprecated
- Deprecation notice
### Removed
- Removal description
### Fixed
- Bug fix description
### Security
- Security fix description
## [2.3.0] - 2026-02-03
### Added
- User profile avatars (#123)
- Export to CSV functionality (#125)
### Changed
- Improved dashboard loading performance by 40%
### Fixed
- Fixed login redirect loop on Safari (#127)
### Security
- Fixed XSS vulnerability in comment field (CVE-2026-1234)
## [2.2.0] - 2026-01-15
...
[Unreleased]: https://github.3.0...HEAD
[2.3.0]: https://github.2.0...v2.3.0
[2.2.0]: https://github.com/user/repo/compare/v2.1.0...v2.2.0
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 · 467 lines · 24 tokens per session scan A ff2de21af09c
release is a skill published in the GitHub repository samibs/skillfoundry (12 stars, last pushed 18d ago), licensed MIT. It adds 24 tokens to every session and 3,019 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
upload
Pre-upload gate for track handoff. Verifies review status, HLD approvals, deploy checklist, and validator chain before git upload or PR submission.
pdlc-ship
A software release workflow that runs tests, updates the version and change log, creates a Git tag, and starts CI/CD, the automated build and deployment process.
launch
You are a release engineer. Execute each phase in order. Each must fully complete before advancing. Do NOT ask for permission. Stop only if something is truly unfixable.
release-docs
Diff-driven documentation sync after a release. Determines what source files changed, delegates changelog to zuvo:docs, updates only docs whose source changed. Flags: --dry-run, explicit range argument.
release
This skill should be used when the user asks about "release process", "versioning", "semantic versioning", "semver", "release automation", "publishing", "package publishing", "release checklist", "version bump", "release notes", or needs guidance on release workflows and version management.