Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/WackyGem/Fleurnpx agentmods add skills/wackygem/fleur/fleur-version-managementWrote 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/wackygem/fleur/fleur-version-management)<a href="https://agentmods.dev/skills/wackygem/fleur/fleur-version-management"><img src="https://agentmods.dev/badge/skills/wackygem/fleur/fleur-version-management/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.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00100 | $0.02543 |
| Opus 5.5 | $0.00040 | $0.01017 |
| Sonnet 5.5 | $0.00020 | $0.00509 |
| Haiku 4.5 | $0.00010 | $0.00254 |
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 1mo 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleur Version Management
使用此 skill 维护 fleur 的版本事实和发布追溯。skill 只保留日常操作流程、决策规则、验证命令和停止条件。
先读事实
- 先按变更范围读取架构事实文档：
docs/architecture/data-platform.mddocs/architecture/data-governance.mddocs/architecture/furnace.mddocs/architecture/rearview.mddocs/architecture/racingline.mddocs/architecture/deploy-ops.md
- 用工具确认当前版本源，不凭记忆改版本：
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 不代表数据平台整体版本。数据平台状态由 scheduler、contract-tools、elt、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。
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.
- 1mo ago First seen · 319 lines · 100 tokens per session scan A 7986986af5de
fleur-version-management is a skill published in the GitHub repository WackyGem/Fleur (138 stars, last pushed 15d ago), licensed MIT. It adds 100 tokens to every session and 2,543 once invoked, about $0.0004 per session on Opus 5.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
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.
release
Fully automate a release with version-bump and childhood.
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
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.