agentleFS
KSEGITKSEGIT/Version-Sentinel/.github/copilot-instructions.md

Version-Sentinel

Copilot instructions6 starsChanged 2 days agoMITView on GitHub

This workspace uses version-sentinel: dependency edits and install commands are blocked (via workspace hooks) until the target version is verified against its upstream registry and recorded. 1. Look up the latest version of the package on its upstream registry: - npm → npmjs.com - pip / pyproject → pypi.org - cargo → crates.io - csproj → nuget.org 2. Record the check by running in the terminal: bash scripts/vs-record.sh <ecosystem> <pkg> <version> <source-url> The source must be the canonical https:// registry…

  • Installs packages
  • Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.

    Of the Copilot instructions files we read, the 2,397 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository6 other files it gives its agents.

The file

We split this copilot-instructions.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Look up the latest version of the package on its upstream registry:

    line 7
  2. Very specific:

    Run bash scripts/check-versions.sh before tagging a release.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 3,854 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
copilot-instructions.md

Version Sentinel

This workspace uses version-sentinel: dependency edits and install commands are blocked (via workspace hooks) until the target version is verified against its upstream registry and recorded.

When a tool call is BLOCKED with "version-sentinel"

  1. Look up the latest version of the package on its upstream registry:
    • npm → npmjs.com
    • pip / pyproject → pypi.org
    • cargo → crates.io
    • csproj → nuget.org
  2. Record the check by running in the terminal: bash scripts/vs-record.sh <ecosystem> <pkg> <version> <source-url> The source must be the canonical https:// registry URL you actually saw, or intentional: <reason> for deliberate pins.
  3. Retry with the exact version you recorded. If the blocked input omitted the version or used a floating tag such as latest, rewrite it first. For example, use npm install lodash@4.17.21, not npm install lodash or npm install lodash@latest.

Local paths, URLs, git sources, and workspace dependencies are outside registry-version checks. A NuGet PackageReference without Version may use Central Package Management, so the manifest gate ignores that form.

Intentional pins

To deliberately install a non-latest version (CVE mitigation, compatibility), record with intentional: <reason> as the source. These show as intentional-pin, not DRIFT, in audits.

Audit

Run bash scripts/check-versions.sh before tagging a release. It scans package.json, requirements*.txt, constraints*.txt, pyproject.toml, Cargo.toml, *.csproj, *.fsproj, and *.vbproj and reports drift without blocking.

Escape hatch

Set VS_DISABLE=1 in the environment to disable blocking for a session (throwaway work only, with the user's awareness).

Mandatory startup audit and recovery

Before dependency work, complete the online startup audit. Missing or invalid manifests require Daniel's explicit approval before recovery. The recorder now performs a successful online upstream check itself; URL-only, offline, and post-install records do not authorize changes. Older pins still need online verification and a reason. Follow the enforcement workflow for audit, recovery, and interception limits.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.