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 instructions/ksegit/version-sentinel/agents-mdgit 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.01027 | $0.01027 |
| Opus 5 | $0.00513 | $0.00513 |
| Sonnet 5 | $0.00205 | $0.00205 |
| Haiku 4.5 | $0.00103 | $0.00103 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 67 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:
-
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>
- npm:
-
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, orintentional:<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" -
Retry the edit or install. With a fresh entry on record, the hook (where present) lets the operation through.
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.
Supported manifests
package.json (npm/pnpm/yarn/bun), requirements*.txt, constraints*.txt, pyproject.toml (pip, Poetry, uv), Cargo.toml, and *.csproj / *.fsproj / *.vbproj (NuGet).
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 · 67 lines · 1,027 tokens per session scan A 21d968db1eba
Version-Sentinel AGENTS.md is an instructions file published in the GitHub repository KSEGIT/Version-Sentinel (3 stars, last pushed 2d ago), licensed MIT. It adds 1,027 tokens to every session, about $0.0051 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 instructions, from other repositories
ai-dev-kit AGENTS.md
Instructions for noah-sheldon/ai-dev-kit, covering ai dev kit — agent instructions, core principles, contributor policy, available agents and agent orchestration.
magi-workflow CLAUDE.md
Instructions for howar31/magi-workflow, covering what this is, slash commands, subagents, project state model and project document tiers.
Cerebro AGENTS.md
Instructions for AgenticFirst/Cerebro, covering cerebro — agent context, read before touching integrations, project layout, conventions a fresh agent would otherwise miss and running locally.
discoclaw CLAUDE.md
Instructions for DiscoClaw/discoclaw, covering discoclaw, safety, context loading (strict), identity and workspace file ownership.
nextjs-skills CLAUDE.md
Instructions for mohamed-hossam1/nextjs-skills: All contribution rules — style, naming, file layout, verification — live in AGENTS.md. Read that first.
claude-plugins CLAUDE.md
Claude Code instructions for aiocean/claude-plugins, covering claude.md, what this is, plugin structure, marketplace registry and plugin categories.