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 commands/ksegit/version-sentinel/vs-recordgit clone --depth 1 https://github.com/KSEGIT/Version-SentinelWhat 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.00012 | $0.00216 |
| Opus 5 | $0.00006 | $0.00108 |
| Sonnet 5 | $0.00002 | $0.00043 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
vs-record 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 yesterday.
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.
What it actually says
Record that a dependency version has been verified. Run after WebSearch/WebFetch/context7 confirms the version.
Usage: /vs-record <ecosystem> <pkg> <version> <source>
Source must be http(s):// URL or intentional:<reason>.
Ecosystems (v0.1): npm, pip, cargo, csproj, pyproject
Examples:
/vs-record npm lodash 4.17.21 https://www.npmjs.com/package/lodash/vs-record pip requests 2.31.0 https://pypi.org/project/requests//vs-record csproj Serilog 3.1.1 intentional: CVE lock pending audit
!bash ${CLAUDE_PLUGIN_ROOT}/scripts/vs-record.sh $ARGUMENTS
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.
- yesterday First seen · 20 lines · 12 tokens per session scan A c774ae7954a1
vs-record is a command published in the GitHub repository KSEGIT/Version-Sentinel (3 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 216 once invoked, about $0.0001 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 commands, from other repositories
build-fix
Fix build and type failures with minimal diffs.
checkpoint
Record a verified checkpoint before the next phase.
doctor
Check the install surface for missing files and invalid manifests.
feature-dev
Drive a feature from plan to implementation to review.
git-agent
Coordinate issue intake, branch work, and merge steps.
install
Install the AI Dev Kit surface into a target directory.