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/nickdesi/ffbb-mcp-server/release-gatenpx skills add nickdesi/FFBB-MCP-Server --skill release-gategit clone --depth 1 https://github.com/nickdesi/FFBB-MCP-ServerWrote 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/nickdesi/ffbb-mcp-server/release-gate)<a href="https://agentmods.dev/skills/nickdesi/ffbb-mcp-server/release-gate"><img src="https://agentmods.dev/badge/skills/nickdesi/ffbb-mcp-server/release-gate.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.00084 | $0.00927 |
| Opus 5 | $0.00042 | $0.00464 |
| Sonnet 5 | $0.00017 | $0.00185 |
| Haiku 4.5 | $0.00008 | $0.00093 |
Grade A, and why
release-gate 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 5d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Gate — FFBB MCP Server
Use this skill for any request involving push, tag, release, publish, version, CI, GitHub Actions, or remote synchronization.
This workflow adapts the relevant patterns from sickn33/antigravity-awesome-skills:
lint-and-validate: validate after changes.verification-before-completion: evidence before success claims.git-pushing: commit and push only when explicitly requested.iterate-pr: follow GitHub checks until green.codebase-audit-pre-push: inspect diffs and side effects before pushing.
Non-negotiable rules
- Use
rtkfor all terminal commands. - Work from the repository root.
- Do not claim completion without fresh command output.
- Do not push, tag, release, or publish if any local gate fails.
- Keep changes surgical; do not refactor unrelated code.
- Inspect and revert unintended runtime/test mutations, especially
src/ffbb_mcp/acronyms_cache.json.
Required local gate before push/tag/release
Run the full gate, in this order:
- Version alignment:
rtk uv run python tools/check_version_alignment.py
- Formatting:
rtk uv run ruff format --check .
- Linting:
rtk uv run ruff check .
- Types:
rtk uv run mypy src
- Tests:
rtk uv run pytest
- Repository inspection:
rtk git status --short --branchrtk git diff --stat- targeted
rtk git diff -- ./pathfor changed files.
If version files changed, run rtk uv run python tools/sync_version.py, inspect the diff, then rerun the required local gate.
Push workflow
Only when the user explicitly asks to push or publish changes:
- Run the required local gate.
- Inspect staged and unstaged changes.
- Revert unrelated changes and generated side effects not intentionally part of the task.
- Commit with a conventional commit message.
- Push the branch.
- Inspect GitHub Actions after pushing:
rtk gh run list --limit 5- For failures, inspect only failed logs with
rtk gh run view <run-id> --log-failed.
- If CI fails, fix the root cause locally, rerun the relevant gate plus any affected tests, commit, push, and re-check CI.
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.
- 5d ago First seen · 101 lines · 84 tokens per session scan A d97707d9eadb
release-gate is a skill published in the GitHub repository nickdesi/FFBB-MCP-Server (2 stars, last pushed today), licensed Apache-2.0. It adds 84 tokens to every session and 927 once invoked, about $0.0004 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-31.
Other skills, from other repositories
changelog-writer
Write changelogs for Bifrost releases. Reads git history, bumps module versions following the core→framework→plugins→transport hierarchy, writes transports/changelog.md (enterprise-style) and per-module changelog.md files, and updates version files. Invoked with /changelog-writer or /changelog-writer .
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…
release-checklist
Pre-release safety audit for the Bifrost repo. Scans database migrations changed in a release for high-scale deadlock / lock-contention risks and for work that blocks application boot time, then produces a pass/warn/fail report with a concrete remediation plan. Invoked with /release-checklist [git-ref-range]. Built to…
portainer-mcp-release
How to cut a portainer-mcp release that bumps the embedded Portainer OpenAPI spec to a new Portainer minor (e.g. 2.41.x → 2.42.x). Walks through finding the upstream patch target, regenerating the spec, recounting ops/tags per profile, refreshing the orphan-tag inventory, bumping version pins across the README and…
release-dbt-mcp
Release a new version of dbt-mcp to PyPi.
release
Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.