What is releasing-fdb?

A release checklist and workflow for publishing new versions of fdb and fdb_helper, two related Flutter debugging packages. It covers version changes, checks, publishing to pub.dev, Git tags, and GitHub releases.

Use it to choose a semantic-version change, update package and documentation versions, run release checks, publish to pub.dev, create tags, and prepare GitHub releases.

It reduces missed steps when releasing the two packages together and helps verify them before publication.

How andrzejchm/fdb configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to andrzejchm/fdb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/andrzejchm/fdb/main/.agents/skills/releasing-fdb/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/andrzejchm/fdb

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andrzejchm/fdb/releasing-fdb/github.svg)](https://agentmods.dev/skills/andrzejchm/fdb/releasing-fdb)

Your own site

<a href="https://agentmods.dev/skills/andrzejchm/fdb/releasing-fdb"><img src="https://agentmods.dev/badge/skills/andrzejchm/fdb/releasing-fdb/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andrzejchm/fdb/releasing-fdb"><img src="https://agentmods.dev/badge/skills/andrzejchm/fdb/releasing-fdb.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 79 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,592 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00079	$0.02592
Opus 5.5	$0.00032	$0.01037
Sonnet 5.5	$0.00016	$0.00518
Haiku 4.5	$0.00008	$0.00259

Measured 11d ago against content hash 30621601e060, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

releasing-fdb scanned grade C with 2 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 11d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -s https://pub.dev/api/packages/fdb | python3 -c "import sys,json; print(json.load(sys.stdin)['latest']['version'])"

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s https://pub.dev/api/packages/fdb | python3 -c "import sys,json; print(json.load(sys.stdin)['latest']['version'])"

.agents/skills/releasing-fdb/SKILL.md · 222 lines

How it starts

The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Semver

Follow Semantic Versioning:

Patch (0.1.x): bug fixes, no API/CLI changes
Minor (0.x.0): new commands, new flags, backward-compatible changes
Major (x.0.0): breaking changes to CLI interface, fdb_helper API, or file contracts

Prerequisites

fdb published on pub.dev: https://pub.dev/packages/fdb
fdb_helper published on pub.dev: https://pub.dev/packages/fdb_helper
Automated publishing enabled for both packages on their respective pub.dev admin pages (GitHub Actions, andrzejchm/fdb, tag pattern v{{version}}, push events):
- https://pub.dev/packages/fdb/admin
- https://pub.dev/packages/fdb_helper/admin
LICENSE, CHANGELOG.md, and README.md present in both repo root and packages/fdb_helper/
gh CLI authenticated: gh auth status

Release Checklist

Copy and track progress:

- [ ] Pre-release verification (analyze, unit tests, smoke tests)
- [ ] Determine version bump type (major / minor / patch)
- [ ] Update version in all 11 files (lockstep): constants.dart, pubspec.yaml, fdb_helper/pubspec.yaml, fdb_helper/lib/src/version.dart, lib/skill/SKILL.md (2 changes: fdb version + fdb_helper version in setup snippet), CHANGELOG.md, fdb_helper/CHANGELOG.md, README.md, example/example.md, doc/README.agents.md (fdb_helper version in snippets)
- [ ] Verify no stale OLD_VERSION references remain (grep check)
- [ ] Commit: `chore: bump version to X.Y.Z`
- [ ] Tag: `git tag vX.Y.Z`
- [ ] Push: `git push origin main --tags`
- [ ] Verify CI workflow passes (analyze, unit tests, pub.dev publish, GitHub release)
- [ ] Post-release verification

Pre-release Verification

All checks must pass before proceeding. Do not skip any step.

task analyze                  # dart analyze + dart format --set-exit-if-changed
task test:unit                # unit tests
task smoke                    # full integration smoke test (requires device/simulator)

If task smoke fails, fix the issue and re-run before continuing. A connected iOS Simulator or Android emulator is required.

Read the full file on GitHub · 222 lines

Changes

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.

11d ago Changed · +6 lines 30621601e060
18d ago Changed · +1 lines 300f8f689dad
1mo ago First seen · 215 lines · 79 tokens per session scan C cfdf97699212

Subscribe to this mod's changes

releasing-fdb is a skill published in the GitHub repository andrzejchm/fdb (46 stars, last pushed 12d ago), licensed MIT. It adds 79 tokens to every session and 2,592 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release

Fully automate a release with version-bump and childhood.

thedotmack/claude-mem · 13 tokens

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.

phuryn/pm-skills · 57 tokens

fdb: Skill for Claude Code