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 skills add ncssm-robotics/ftc-claude --skill versioninggit clone --depth 1 https://github.com/ncssm-robotics/ftc-claudeWrote 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/ncssm-robotics/ftc-claude/versioning)<a href="https://agentmods.dev/skills/ncssm-robotics/ftc-claude/versioning"><img src="https://agentmods.dev/badge/skills/ncssm-robotics/ftc-claude/versioning.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.1 | $0.00045 | $0.00972 |
| Opus 5 | $0.00023 | $0.00486 |
| Sonnet 5 | $0.00009 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
versioning 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 8d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FTC Versioning Guardrail
STOP: Do Not Manually Change Version Numbers!
This repository uses an automated release process. Contributors should NEVER manually change version numbers in any file.
Files You Should NOT Edit (Version Fields)
| File | Field | Why Not |
|---|---|---|
plugins/<name>/plugin.json |
version |
Release script updates this |
plugins/<name>/skills/<name>/SKILL.md |
metadata.version |
Release script updates this |
.claude-plugin/marketplace.json |
plugin version |
Release script updates this |
The Correct Workflow
For Contributors
-
Make your changes to the skill (SKILL.md, scripts, etc.)
-
Add changelog entries to
## [Unreleased]section in CHANGELOG.md:## [Unreleased] ### Added - New calibration script for pod offset calculation ### Fixed - Corrected coordinate transformation formula -
Use the update-skill command to help generate entries:
/update-skill <skill-name> -
Submit PR to the
developbranch -
Done! - Versions are bumped automatically during the release process
For Maintainers (Release Process)
- Go to GitHub Actions
- Run "Prepare Release" workflow
- Script automatically:
- Parses changelog categories (Added → MINOR, Fixed → PATCH, etc.)
- Calculates new version numbers
- Updates all three version locations atomically
- Creates release PR
Why This Matters
Deterministic Versioning
Version bumps are calculated from changelog categories:
| Changelog Category | Version Bump |
|---|---|
### Removed |
MAJOR (X.0.0) |
### Changed |
MAJOR (X.0.0) |
### Added |
MINOR (0.Y.0) |
### Deprecated |
MINOR (0.Y.0) |
### Fixed |
PATCH (0.0.Z) |
### Security |
PATCH (0.0.Z) |
Consistency Guarantee
The release script ensures:
- All three version locations match
- Changelog is properly formatted
- Release notes are generated
- Git tags are created
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.
- 8d ago First seen · 129 lines · 45 tokens per session scan A 53de91ea1e32
versioning is a skill published in the GitHub repository ncssm-robotics/ftc-claude (4 stars, last pushed 7mo ago), licensed MIT. It adds 45 tokens to every session and 972 once invoked, about $0.0002 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-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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
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.
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".
updater_guide
Guidance for checking for and installing Row-Bot updates.