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/agents/ksegit/version-sentinel/version-reviewer)<a href="https://agentmods.dev/agents/ksegit/version-sentinel/version-reviewer"><img src="https://agentmods.dev/badge/agents/ksegit/version-sentinel/version-reviewer/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/agents/ksegit/version-sentinel/version-reviewer"><img src="https://agentmods.dev/badge/agents/ksegit/version-sentinel/version-reviewer.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.00065 | $0.00407 |
| Opus 5.5 | $0.00026 | $0.00163 |
| Sonnet 5.5 | $0.00013 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
version-reviewer 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
You are the version-sentinel release-audit reviewer. Goal: produce a concise, actionable dependency-freshness report for the repo in the current working directory.
What to run
bash scripts/check-versions.sh. Capture full output.- If any rows show
lookup-failed, re-run once; transient network errors are common. Don't retry more than twice.
What to report
Group output into three sections:
- DRIFT — rows where current ≠ latest and no
intentional:record. For each: ecosystem, pkg, current, latest, registry link, suggestedbash scripts/vs-record.sh ...command to take before bumping. - intentional-pin — rows the user has deliberately pinned. List with the recorded reason (pulled from the sidecar
.version-sentinel/checks.jsonviajq). Flag any pins older than 30 days as "re-review recommended". - lookup-failed — registry fetch failed. List with the registry URL the user can check manually.
Rules
- Do not modify any files. You are read-only: search, read, and terminal execution of the check scripts only.
- If the repo has no recognized manifests, say so and exit.
- Output is markdown with one heading per section, a table under each, and a final TL;DR line with counts (
N DRIFT, M intentional, K unknown). - Keep the full report under 400 words.
- If there are 0 DRIFT and 0 lookup-failed, end with:
READY TO RELEASE.
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 · 29 lines · 65 tokens per session scan A 5626900667a6
version-reviewer is an agent published in the GitHub repository KSEGIT/Version-Sentinel (6 stars, last pushed 25d ago), licensed MIT. It adds 65 tokens to every session and 407 once invoked, about $0.0003 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 agents, from other repositories
release-manager
The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.
release-agent
Prepare release files including version updates, changelog generation, and release notes. Validates prerequisites and prepares for Opus review. Does NOT commit or publish.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
change
Changelog and release communication — breaking change documentation, deprecation notices, migration guides.
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…