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/bostonaholic/team/version-bumpnpx skills add bostonaholic/team --skill version-bumpgit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/version-bump)<a href="https://agentmods.dev/skills/bostonaholic/team/version-bump"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/version-bump.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.00207 | $0.05315 |
| Opus 5 | $0.00103 | $0.02658 |
| Sonnet 5 | $0.00041 | $0.01063 |
| Haiku 4.5 | $0.00021 | $0.00532 |
Grade A, and why
version-bump 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 today.
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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Bump — version a Team PR at land time
Follow
skills/principle-progress-tracking/SKILL.md: this procedure has more than two steps — seed one todo item per step below before starting and mark each complete as you go.
This skill versions the Team plugin itself at land time. It is dev-only
(lives under .claude/, never distributed to plugin users). Tagging and the
GitHub release are not part of this procedure — release-on-merge.yml does
both automatically when the PR merges. Full policy:
docs/versioning.md.
The dev land process
Landing a Team PR is two steps, in order:
- Bump (this skill). Run
version-bumpagainst currentmain. It picks the level, assigns the next free version, and bumps the six version strings. It cuts the[Unreleased]changelog into a dated## [X.Y.Z]section, runs the land-time consistency assertion, and commitschore(version): X.Y.Z. - Land (the generic
/shipitskill). Run the distributed runtime/shipitskill to push the branch, wait for CI, and squash-merge.shipitis project-agnostic — it does no versioning. This skill is the Team-internal bumper it composes with.
Run this skill before /shipit, against the version of main you intend to
land onto.
Precondition — explicit land intent
Everything below is irreversible-ish work on a shared number: it rewrites six
version strings, moves the [Unreleased] changelog body into a dated section,
retitles the PR, and commits. All of it is computed against the base
branch's tip at this moment, so a bump made any earlier than the land is
stale the moment another PR merges — and the pre-merge guard then denies the
merge until someone recomputes it. Deferring to land time is what keeps the
number correct.
This skill fires only on explicit land intent, meaning one of:
- The user asked to land: "ship it", "land the PR", "land this",
/shipit. - The user asked for the bump itself: "bump the version", "version this PR".
- A
/shipitrun is already in flight and reached its versioning step.
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.
- today Changed · +2 lines ebc3ce294a99
- 4d ago First seen · 398 lines · 207 tokens per session scan A 4c411183b40d
version-bump is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 207 tokens to every session and 5,315 once invoked, about $0.0010 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.
Other skills, from other repositories
analyze-performance-traces
Analyze Chrome, Chromium, Electron, React DevTools, or Perfetto-compatible JSON traces and audit user-reported profiling findings without loading large artifacts into context; prove trigger-to-render/layout chains, separate measured facts from source inference, find exact code choke points, classify forced layout and…
tutti-test-audit
Audit, design, write, materially revise, or remove Tutti tests. Use whenever Codex changes or reviews unit, component, conformance, integration, regression, platform, or repository tests; enforce a protected product contract, credible failure, correct owning boundary, negative-control evidence, overlap review…
tutti-agent-workspace-app
Build or evolve a complex agent-enabled Tutti workspace app repository. Use for Tutti apps with web/server/shared monorepos, @tutti-os/agent-acp-kit local agent runtimes, kit-owned TUTTICLI agent/composer discovery, dynamic agent catalogs, run-scoped MCP tool gateways, app-owned package builders, web-first debugging…
assimilate-popular-workflows
This skill should be used when the user asks to "find skills in the wild", "assimilate popular workflows", "discover SKILL.md files in repos", "research external skills", "find workflow patterns", "survey the skill landscape", "what skills exist out there", or wants to investigate public repositories for extractable…
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
babysit
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.).