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/flipt-io/mcp-server-flipt/releasenpx skills add flipt-io/mcp-server-flipt --skill releasegit clone --depth 1 https://github.com/flipt-io/mcp-server-fliptWrote 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/flipt-io/mcp-server-flipt/release)<a href="https://agentmods.dev/skills/flipt-io/mcp-server-flipt/release"><img src="https://agentmods.dev/badge/skills/flipt-io/mcp-server-flipt/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.00085 | $0.01266 |
| Opus 5 | $0.00043 | $0.00633 |
| Sonnet 5 | $0.00017 | $0.00253 |
| Haiku 4.5 | $0.00009 | $0.00127 |
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 4d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release a package
Releases one package per invocation. Arguments (ask if missing): which package (v1 or v2) and the bump (patch | minor | major | explicit X.Y.Z).
| v1 | v2 | |
|---|---|---|
| npm package | @flipt-io/mcp-server-flipt |
@flipt-io/mcp-server-flipt-v2 |
| directory | packages/mcp-server-flipt |
packages/mcp-server-flipt-v2 |
| git tag | vX.Y.Z |
[email protected] |
| docker image | ghcr.io/flipt-io/mcp-server-flipt |
ghcr.io/flipt-io/mcp-server-flipt-v2 |
Tags drive .github/workflows/publish.yml (npm + ghcr, each image also tagged :latest).
CRITICAL — tag scheme: a vX.Y.Z tag ALWAYS publishes the v1 package, regardless of what was bumped. Never create a v* tag for a v2 release, and never let pnpm version auto-tag (its default tag is v*). Always pass --no-git-tag-version and create the tag by hand.
Procedure
1. Preflight
git switch main && git pull --ff-only
git status --short # must be clean; abort if not
pnpm install
pnpm -r check && pnpm lint && pnpm -r test && pnpm -r build
All gates must pass before bumping. Also confirm CI is green on origin/main (gh run list --branch main --limit 3). If releasing a fix that just merged, make sure it's actually in main.
2. Bump
Run inside the package directory (the version lifecycle script regenerates src/version.ts and git adds it — a test fails if it drifts, so never edit version fields by hand):
cd packages/<dir>
pnpm version <patch|minor|major|X.Y.Z> --no-git-tag-version
cd ../..
Confirm packages/<dir>/src/version.ts matches the new package.json version and both are staged/modified. Set NEW_VERSION from the package.json.
3. Commit and tag
git add packages/<dir>/package.json packages/<dir>/src/version.ts
# v1:
git commit -m "chore(release): mcp-server-flipt v${NEW_VERSION}"
git tag "v${NEW_VERSION}"
# v2:
git commit -m "chore(release): mcp-server-flipt-v2 ${NEW_VERSION}"
git tag "mcp-server-flipt-v2@${NEW_VERSION}"
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.
- 4d ago First seen · 102 lines · 85 tokens per session scan A 352b3f02a6b2
release is a skill published in the GitHub repository flipt-io/mcp-server-flipt (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 85 tokens to every session and 1,266 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
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.