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 commands/samibs/skillfoundry/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/commands/samibs/skillfoundry/release)<a href="https://agentmods.dev/commands/samibs/skillfoundry/release"><img src="https://agentmods.dev/badge/commands/samibs/skillfoundry/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.00000 | $0.02986 |
| Opus 5 | $0.00000 | $0.01493 |
| Sonnet 5 | $0.00000 | $0.00597 |
| Haiku 4.5 | $0.00000 | $0.00299 |
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 yesterday.
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 — 461 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.
- yesterday First seen · 461 lines · 0 tokens per session scan A f7f0bccea019
release is a command published in the GitHub repository samibs/skillfoundry (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,986 tokens. 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 commands, from other repositories
release
Create a versioned release: update CHANGELOG, bump version, validate, commit, push, and publish a GitHub Release.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.