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 pjt222/agent-almanac --skill apply-semantic-versioninggit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/apply-semantic-versioning)<a href="https://agentmods.dev/skills/pjt222/agent-almanac/apply-semantic-versioning"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/apply-semantic-versioning/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/pjt222/agent-almanac/apply-semantic-versioning"><img src="https://agentmods.dev/badge/skills/pjt222/agent-almanac/apply-semantic-versioning.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.00094 | $0.02285 |
| Opus 5.5 | $0.00038 | $0.00914 |
| Sonnet 5.5 | $0.00019 | $0.00457 |
| Haiku 4.5 | $0.00009 | $0.00229 |
Grade A, and why
apply-semantic-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 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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply Semantic Versioning
Determine and apply the correct semantic version bump by analyzing changes since the last release. This skill reads version files, classifies changes as breaking (major), feature (minor), or fix (patch), computes the new version number, and updates the appropriate files. Follows SemVer 2.0.0 specification.
When to Use
- Preparing a new release and need to determine the correct version number
- After merging a set of changes and before tagging a release
- Evaluating whether a change constitutes a breaking change
- Adding pre-release identifiers (alpha, beta, rc) to a version
- Resolving disagreement about what version bump is appropriate
Inputs
- Required: Project root directory containing a version file (DESCRIPTION, package.json, Cargo.toml, pyproject.toml, or VERSION)
- Required: Git history since the last release (tag or commit)
- Optional: Commit convention in use (Conventional Commits, free-form)
- Optional: Pre-release label to apply (alpha, beta, rc)
- Optional: Previous version if not readable from files
Procedure
Step 1: Read Current Version
Locate and read the version file in the project root.
# R packages
grep "^Version:" DESCRIPTION
# Node.js
grep '"version"' package.json
# Rust
grep '^version' Cargo.toml
# Python
grep 'version' pyproject.toml
# Plain file
cat VERSION
Parse the current version into major.minor.patch components. If the version contains a pre-release suffix (e.g., 1.2.0-beta.1), note it separately.
Got: Current version identified as MAJOR.MINOR.PATCH[-PRERELEASE].
If fail: If no version file is found, check for a VERSION file or git tags (git describe --tags --abbrev=0). If no version exists at all, start at 0.1.0 for initial development or 1.0.0 if the project has a stable public API.
Step 2: Analyze Changes Since Last Release
Retrieve the list of changes since the last tagged release.
# Find the last version tag
git describe --tags --abbrev=0
# List commits since that tag
git log --oneline v1.2.3..HEAD
# If using Conventional Commits, filter by type
git log --oneline v1.2.3..HEAD | grep -E "^[a-f0-9]+ (feat|fix|BREAKING)"
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 · 220 lines · 94 tokens per session scan A 96fd9884a79a
apply-semantic-versioning is a skill published in the GitHub repository pjt222/agent-almanac (42 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 2,285 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-09-03.
Other skills, from other repositories
ship
Enter the Ship phase of CocoBrew. Reads review.md approval, generates structured commit, creates semantic version tag, optionally creates PR via gh CLI, and records deployment details. Requires approved review.
capgo-release-management
Runs Capgo OTA release operations with the CLI, including bundle upload (channels, delta, rollout, encryption, version bumps), bundle compatibility and releaseType checks, channel add/set/promote/currentBundle/delete, progressive rollouts and rollback, bundle cleanup, preview QR codes, and key create/save encryption…
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…
audit-pr
Audit a whole PR against the delivery contract and return MERGE-READY or evidenced blockers with the full URL. Consumes the current review-change REVIEW-PASS receipt instead of re-running review axes; posts a SHA-bound ready comment; never edits or merges. Triggers: "audit-pr", "is this PR ready", "merge gate".
execute-phase
Step executor for units whose triage (unit-lane) decided which steps the unit needs. Implements one triaged step (or all remaining steps), with frozen acceptance, step-local gates, commits, red-gate repair, and diff-size guard. BREAKING: replaced PLAN.md/TASKS.md/progress.md/ACCEPTANCE.md with the unit doc's Tasks…
release-notes
Summarize a logical grouping of git commits into plain-language release notes for non-technical readers. Use when the user asks for release notes, what changed, a summary of commits, a plain-English changelog, or an easy-to-read bullet list of work at a specific reading level (default 8th grade). Ask which boundary to…