Version-Sentinel: Instructions file for Claude Code

AGENTS.md

Version-Sentinel AGENTS.md is an instructions file for Claude Code, Codex, OpenCode from KSEGIT/Version-Sentinel. It costs 1,211 tokens per session, scanned A, original, MIT.

Dependency-checking instructions for Version Sentinel, a guardrail that verifies package versions against their upstream registries before changes are made. A dependency is an external package a project relies on.

In plain words
What is it for?
Use them when changing dependencies in npm, Python, Rust, or .NET project manifests, including recording the checked version and handling blocked changes.
Why use it?
They prevent stale, invented, or potentially compromised versions from being added, upgraded, downgraded, or installed without a recorded source check.

Instructions file for Claude CodeCodexOpenCode

Written for Claude Code and Codex and OpenCode: PreToolUse hook event, but also the file is AGENTS.md. Also seen: mentions .claude-plugin; mentions Claude Code; mentions AGENTS.md.

This is KSEGIT/Version-Sentinel's own configuration. It tells Claude Code, Codex and OpenCode how to work on Version-Sentinel itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Version-Sentinel configures →

Reuse

Borrowing it

Nothing to install: this file belongs to KSEGIT/Version-Sentinel. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/KSEGIT/Version-Sentinel/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/KSEGIT/Version-Sentinel

Made for: Claude Code, Codex, OpenCode.

Wrote 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.

agentmods badge for Version-Sentinel AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/ksegit/version-sentinel/agents-md/github.svg)](https://agentmods.dev/instructions/ksegit/version-sentinel/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/ksegit/version-sentinel/agents-md"><img src="https://agentmods.dev/badge/instructions/ksegit/version-sentinel/agents-md/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.

agentmods 80×15 button for Version-Sentinel AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/ksegit/version-sentinel/agents-md"><img src="https://agentmods.dev/badge/instructions/ksegit/version-sentinel/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,211 This file is loaded in full into every session.
When invoked 1,211 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01211 $0.01211
Opus 5.5 $0.00484 $0.00484
Sonnet 5.5 $0.00242 $0.00242
Haiku 4.5 $0.00121 $0.00121

Measured 1mo ago against content hash 4df34e3989b9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

Version-Sentinel AGENTS.md 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.

AGENTS.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Version Sentinel — Cross-Agent Instructions

Version Sentinel is a guardrail that prevents stale, hallucinated, or compromised dependency versions from reaching your manifests. Before any dependency is added, bumped, downgraded, or installed, the agent must verify the intended version against its upstream registry and record that check. Checks are stored in .version-sentinel/checks.json and expire after a freshness window (default 24h).

Required workflow when a dependency change is blocked

If a hook blocks an edit or install (exit 2, BLOCKED: version-sentinel), or if you are about to change any dependency on a platform without hooks:

  1. Look up the latest version on the upstream registry via web search or fetch:

    • npm: https://www.npmjs.com/package/<pkg>
    • pip / pyproject: https://pypi.org/project/<pkg>/
    • cargo: https://crates.io/crates/<pkg>
    • csproj (NuGet): https://www.nuget.org/packages/<pkg>
  2. Record the check:

    bash scripts/vs-record.sh <ecosystem> <pkg> <version> <source-url-or-intentional:reason>
    

    The source must be an http(s):// URL you actually consulted, or intentional:<reason> for deliberate pins (e.g. CVE lock, compatibility). Example:

    bash scripts/vs-record.sh npm lodash 4.17.21 https://www.npmjs.com/package/lodash
    bash scripts/vs-record.sh csproj Serilog 3.1.1 "intentional: CVE lock pending audit"
    
  3. Retry with the verified version. If the blocked edit or command omitted the version or used a floating tag such as latest, replace it with the exact version you recorded. For example, retry npm install [email protected], not npm install lodash or npm install lodash@latest.

Never fabricate a source URL you did not actually consult, and never bypass the record step to force a dependency change through.

Audit

bash scripts/check-versions.sh

Scans manifests within 4 directory levels of the current directory, compares each dependency against its upstream registry, and reports drift. Intentional pins show as intentional-pin, not DRIFT. Run before tagging a release.

Read the full file on GitHub · 73 lines

Changes

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.

  1. 1mo ago Changed · +2 lines · +113 tokens per session 4df34e3989b9
  2. 1mo ago Changed · +4 lines · +71 tokens per session aa20fa7ebec8
  3. 1mo ago First seen · 67 lines · 1,027 tokens per session scan A 21d968db1eba

Subscribe to this mod's changes

Version-Sentinel AGENTS.md is an instructions file published in the GitHub repository KSEGIT/Version-Sentinel (6 stars, last pushed 26d ago), licensed MIT. It adds 1,211 tokens to every session, about $0.0048 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,649 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,257 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,159 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens