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 SSWConsulting/SSW.VerticalSliceArchitecture --skill bump-versiongit clone --depth 1 https://github.com/SSWConsulting/SSW.VerticalSliceArchitectureWrote 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/sswconsulting/ssw.verticalslicearchitecture/bump-version)<a href="https://agentmods.dev/skills/sswconsulting/ssw.verticalslicearchitecture/bump-version"><img src="https://agentmods.dev/badge/skills/sswconsulting/ssw.verticalslicearchitecture/bump-version/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/sswconsulting/ssw.verticalslicearchitecture/bump-version"><img src="https://agentmods.dev/badge/skills/sswconsulting/ssw.verticalslicearchitecture/bump-version.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.00086 | $0.00832 |
| Opus 5 | $0.00043 | $0.00416 |
| Sonnet 5 | $0.00017 | $0.00166 |
| Haiku 4.5 | $0.00009 | $0.00083 |
Grade A, and why
bump-version 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 9d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What "bump the version" means in this repo
This repo is a dotnet new template published to NuGet as SSW.VerticalSliceArchitecture.Template. The release is push-triggered, not tag-triggered.
.github/workflows/package.yml runs only when a push to main changes VerticalSliceArchitecture.nuspec. When it does, it:
- Packs the template with
nuget pack. - Pushes the
.nupkgto NuGet.org. - Reads
<version>from the nuspec and creates a matching git tag. - Publishes a GitHub release on that tag with auto-generated notes.
So the <version> value in VerticalSliceArchitecture.nuspec is the release. Changing it and merging to main ships a new package. Nothing else cuts a release.
Versioning scheme: CalVer
Versions are calendar dates, YYYY.MM.DD (e.g. 2025.12.10, 2026.06.12). There is no SemVer major/minor/patch decision — the new version is simply today's date.
To find the latest published version, use gh release view --json tagName -q .tagName — that's authoritative. Don't trust git tag --sort=-v:refname | head: the repo has both v-prefixed and bare tags (v2025.10.24 and 2025.12.10), and the mixed namespace makes that sort return a stale tag above the real latest.
Steps
- Read the current
<version>fromVerticalSliceArchitecture.nuspec. - Compute today's date as
YYYY.MM.DD. That is the new version. - Guard against a same-day re-release: run
git fetch --tagsfirst (release tags are created by CI on the remote, so a local-onlygit tagcan miss one shipped earlier today), then check the date isn't already a tag. If it is, a release already shipped today — append a numeric suffix (YYYY.MM.DD.1) or ask the user how they want to disambiguate. Don't silently overwrite. - Update
<version>to the new value. - Refresh
<releaseNotes>: summarise what changed since the last release. The<version>you read in step 1 (before bumping) is the previous release's tag, so use it as the changelog base:git log --oneline <previous-version>..HEAD. Distil that into a short, human summary (one or two sentences). This is the NuGet page blurb — GitHub generates the full PR-list notes separately, so keep it terse. - Run the
humanizerskill over the release-notes prose before finishing (per the repo/global content-writing rule).
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.
- 9d ago First seen · 44 lines · 86 tokens per session scan A d4b6477928e5
bump-version is a skill published in the GitHub repository SSWConsulting/SSW.VerticalSliceArchitecture (398 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 832 once invoked, about $0.0004 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
release
Prepare and publish Perigon.CLI patch releases, including versioning, release notes, bilingual docs, validation, and the nuget-branch CI handoff.
update-changelog
Update the CHANGELOG.md files of C# projects. Parameters: csroot C# SDK repository root.
create-release
Create a versioned GitHub release with changelog.
safe-github-push
A workflow for safely pushing Git repositories that contain large assets or binary files to GitHub. It checks repository changes and file sizes before planning commits and pushes.
maf-release-watcher
Detects new MAF releases, extracts breaking changes, and keeps the toolkit's registry/matrix/guide current. Pipeline: (1) deterministic data extraction via GitHub Actions + Python helpers + dotnet-inspect, opens a PR with raw data and TODOs on a per-version branch (never commits direct to main), (2) optionally, a…
release-notes
Generate release notes from git history and CHANGELOG. Formats for GitHub Release, Slack, or email. Use before tagging a release.