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.
git clone --depth 1 https://github.com/KSEGIT/Version-SentinelWrote 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/commands/ksegit/version-sentinel/vs-record)<a href="https://agentmods.dev/commands/ksegit/version-sentinel/vs-record"><img src="https://agentmods.dev/badge/commands/ksegit/version-sentinel/vs-record/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/commands/ksegit/version-sentinel/vs-record"><img src="https://agentmods.dev/badge/commands/ksegit/version-sentinel/vs-record.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00287 |
| Opus 5.5 | $0.00005 | $0.00115 |
| Sonnet 5.5 | $0.00002 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00029 |
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 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.
What it actually says
Record that a dependency version has been verified. Run after a web search or registry fetch confirms the version.
Usage: /vs-record <ecosystem> <pkg> <version> <source>
Source must be an 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"
Use the terminal tool to run bash scripts/vs-record.sh with the arguments the user supplied, exactly as given. When the fourth argument is an intentional-pin reason, pass it as ONE quoted argument preserving the "intentional: " format. Relay the script's output verbatim to the user. If the script fails, show its stderr and do not retry with modified arguments unless the user asks.
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 Changed · +1 lines 327a98e2c8c0
- 1mo ago First seen · 20 lines · 12 tokens per session scan A c774ae7954a1
vs-record is a command published in the GitHub repository KSEGIT/Version-Sentinel (6 stars, last pushed 26d ago), licensed MIT. It adds 12 tokens to every session and 287 once invoked, about $0.0000 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-08-31.
Other commands, from other repositories
ai-trend-tracker
Ask ai-trend-tracker about AI/ML news, tools, papers, courses, channels, or learning paths — always live-searched and cited.
kickoff
A project-start command that runs product requirements, work breakdown, and design steps in sequence. It can ask decisions at each step or run automatically with --auto.
verify
A verification command that runs a test agent and a code-review agent in the same round, then combines their results.
ship
A delivery command that runs packaging and reporting steps, then bundles the project’s documentation, test results, and built files into an archive.
build-web
A frontend-building command that follows six visible steps: explore, plan, approve, implement, verify, and summarize. It uses project API and product documents as its starting point.
design-execute
A command that turns a design brief into an attachment package and instructions for Claude Design, Figma, or v0, tools used to create interface designs. It then accepts the returned design source for use in a web project.