fleur-version-management

fleur-version-management is a skill for Claude Code, Codex from WackyGem/Fleur. It costs 100 tokens per session (2,543 once invoked), scanned A, original, MIT.

A procedure for keeping Fleur’s version information accurate and tracing releases back to their source files and commits. A commit is a saved snapshot in Git, the version-control system.

In plain words
What is it for?
It helps find version sources, inspect tags and repository state, update release facts, and check database and package revisions before publishing.
Why use it?
It prevents version changes and release tags from being based on memory or on uncommitted work.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/wackygem/fleur/fleur-version-management
Any agent
npx skills add WackyGem/Fleur --skill fleur-version-management
Clone the repo
git clone --depth 1 https://github.com/WackyGem/Fleur

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.

agentmods badge for fleur-version-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/wackygem/fleur/fleur-version-management.svg)](https://agentmods.dev/skills/wackygem/fleur/fleur-version-management)
Your own site
<a href="https://agentmods.dev/skills/wackygem/fleur/fleur-version-management"><img src="https://agentmods.dev/badge/skills/wackygem/fleur/fleur-version-management.svg" alt="Measured on agentmods" height="20"></a>
Per session 100 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,543 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00100 $0.02543
Opus 5 $0.00050 $0.01272
Sonnet 5 $0.00020 $0.00509
Haiku 4.5 $0.00010 $0.00254

Measured 4d ago against content hash 7986986af5de, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fleur-version-management 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.

docs/skills/fleur-version-management/SKILL.md · 319 lines

How it starts

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

Fleur Version Management

使用此 skill 维护 fleur 的版本事实和发布追溯。skill 只保留日常操作流程、决策规则、验证命令和停止条件。

先读事实

  1. 先按变更范围读取架构事实文档:
    • docs/architecture/data-platform.md
    • docs/architecture/data-governance.md
    • docs/architecture/furnace.md
    • docs/architecture/rearview.md
    • docs/architecture/racingline.md
    • docs/architecture/deploy-ops.md
  2. 用工具确认当前版本源,不凭记忆改版本:
rg -n "^(name|version|version\\.workspace|\\[workspace\\.package\\]|release:|components:|database_heads:)" \
  pipeline/pyproject.toml \
  pipeline/scheduler/pyproject.toml \
  pipeline/contract_tools/pyproject.toml \
  pipeline/elt/dbt_project.yml \
  engines/Cargo.toml \
  engines/crates/*/Cargo.toml \
  app/racingline/package.json \
  deploy/release-manifest.yml 2>/dev/null

rg -n "^version:" pipeline/contracts/datasets
rg -n "revision =|down_revision =" pipeline/migrate/versions

如果用户要求打 tag,先读:

git status --short
git tag --list | sort
git rev-parse --short HEAD

不要在脏工作区里创建 tag,除非用户明确要求 tag 指向当前脏工作区对应的已提交 commit;Git tag 只能指向 commit,不能包含未提交改动。

版本主体

主体 版本源 类型
pipeline workspace meta pipeline/pyproject.toml 仅 meta package SemVer
scheduler pipeline/scheduler/pyproject.toml Component SemVer
contract-tools pipeline/contract_tools/pyproject.toml Component SemVer
contracts datasets pipeline/contracts/datasets/*.yml Dataset integer version
elt pipeline/elt/dbt_project.yml Component SemVer
migrate pipeline/migrate/versions/** Alembic revision
Rust crates engines/crates/*/Cargo.toml Component SemVer
racingline app/racingline/package.json Component SemVer
deploy snapshot deploy/release-manifest.yml Integration manifest

pipeline root version 不代表数据平台整体版本。数据平台状态由 schedulercontract-toolselt、dataset contract versions 和 Alembic heads 共同表达。

判断 bump

先确定影响主体,再确定 bump 级别。

Component SemVer

MAJOR.MINOR.PATCH

  • MAJOR:进入 1.0.0 后用于破坏性 API/CLI/HTTP/dbt model/deploy contract 变化。
  • MINOR:新增向后兼容能力、字段、命令、模型或可选配置。
  • PATCH:bug fix、性能优化、内部重构、文档修正,不改变外部 contract。

Read the full file on GitHub · 319 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.

  1. 4d ago First seen · 319 lines · 100 tokens per session scan A 7986986af5de

Subscribe to this mod's changes

fleur-version-management is a skill published in the GitHub repository WackyGem/Fleur (112 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session and 2,543 once invoked, about $0.0005 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.

Related

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.

openai/symphony · 42 tokens

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

telepresenceio/telepresence · 60 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

mate-oss-gate

在准备把 MateCloud(或其子集)开源 / 发布到公开仓前使用。按 open-core 边界把关:剥离企业代码、清竞品名与内部路径、查密钥、确认 LICENSE。当用户说"要开源了""发布公开版""开源前检查""oss release"时触发。.

mateaix/matecloud · 81 tokens

devops/changelog-generation

自动生成 CHANGELOG,基于 git 提交历史和 pipeline 产物信息,遵循 Conventional Commits 和 Keep a Changelog 规范.

echoVic/boss-skill · 36 tokens

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

Mathews-Tom/armory · 67 tokens