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/fortiumpartners/ensemble/ensemble-releasenpx skills add FortiumPartners/ensemble --skill ensemble-releasegit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/ensemble-release)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/ensemble-release"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/ensemble-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.1 | $0.00027 | $0.01912 |
| Opus 5 | $0.00014 | $0.00956 |
| Sonnet 5 | $0.00005 | $0.00382 |
| Haiku 4.5 | $0.00003 | $0.00191 |
Grade A, and why
ensemble-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 6d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ensemble Command: /ensemble:release
This Codex skill mirrors the Ensemble slash command /ensemble:release.
Follow the workflow below, adapt to the current repository, and keep outputs structured.
This command orchestrates the complete release workflow from quality gates through deployment and verification. It delegates to release-agent for workflow orchestration, coordinating with specialized agents (code-reviewer, test-runner, playwright-tester, deployment-orchestrator) to ensure safe, reliable releases with comprehensive smoke test coverage and automated rollback.
Workflow
Phase 1: Release Initialization
1. Version Validation Validate semantic version format (X.Y.Z)
- Parse --version argument
- Validate semantic versioning format
- Check for version conflicts (tag/branch exists)
2. Release Type Validation Validate release type and workflow selection
- Parse --type argument (standard, hotfix, rollback)
- Determine base branch (main, develop, production)
- Determine target branch (release/vX.Y.Z, hotfix/vX.Y.Z)
- Validate branch arguments if provided
3. Release Branch Creation Create release branch via git-workflow
- Create release branch from base
- Push to remote
- Verify branch created successfully
Delegation: @git-workflow Base and target branches, release version
4. Changelog Generation Generate changelog from git history
- Parse commits since last release
- Categorize changes (breaking, new, enhancement, bugfix)
- Generate markdown formatted changelog
- Add changelog to release branch
Phase 2: Quality Gates
1. Security Scan Execute security vulnerability scan via code-reviewer
- Scan for OWASP Top 10 vulnerabilities
- Check for critical and high-severity issues
- Generate security report
- Block on critical/high issues
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.
- 6d ago First seen · 292 lines · 27 tokens per session scan A fed232ac1009
ensemble-release is a skill published in the GitHub repository FortiumPartners/ensemble (11 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,912 once invoked, about $0.0001 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
install
This skill should be used when the user asks to "install pikiclaw", "build and install", "deploy locally", "update local binary", "release", or "publish".
cli-forge-github
Audit and fix GitHub repository health: rulesets vs CI alignment, branch hygiene, PR lifecycle, release automation flow, permission issues, and transient CI failures. Detects misconfigurations that cause PRs to hang, CI to fail silently, branches to accumulate, and releases to stall. Use when the user says 'PR stuck'…
cli-git-conventional
Enforce Conventional Commits v1.0.0, SemVer 2.0.0, branch naming, commit guard, full-directory AI marker audits, and human ghostwriter style on all git/jj operations. Zero AI markers. Use on 'commit', 'branch', 'tag', 'release', 'changelog', 'semver', 'bump version', 'next version', 'CHANGELOG.md', 'audit markers'…
skillshare-changelog
Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…
release-expert
Multi-repo release coordination: version alignment, RC lifecycle, release waves, rollback planning. Use when saying "release", "version alignment", or "cut an RC".
publish-plugins
(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests.