semver-plugin AGENTS.md

Project instructions for applying Semantic Versioning 2.0.0, a standard for choosing software version numbers. The rules base each version change on what happened to the public API.

In plain words
What is it for?
Use it when reviewing changes and recommending the smallest safe version bump, while checking the actual public API and the project's pre-1.0 policy.
Why use it?
It prevents release versions from being chosen by guesswork, commit labels, or change size. It explains when to use a major, minor, or patch increase and how pre-release versions compare.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/lenoseibert/semver-plugin/agents-md
Clone the repo
git clone --depth 1 https://github.com/LenoSeibert/semver-plugin

Made for: Codex, OpenCode.

Per session 274 This file is loaded in full into every session.
When invoked 274 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00274 $0.00274
Opus 5 $0.00137 $0.00137
Sonnet 5 $0.00055 $0.00055
Haiku 4.5 $0.00027 $0.00027

Measured 2d ago against content hash 5d7b3637b033, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

semver-plugin 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 2d 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 · 24 lines

What it actually says

Semantic Versioning 2.0.0

When a task concerns release versions, apply the official Semantic Versioning 2.0.0 specification. Base the decision on changes to the declared public API, not on commit labels, diff size, or perceived importance.

  • Incompatible public API change: increment MAJOR; reset minor and patch.
  • Backward-compatible functionality or deprecation: increment MINOR; reset patch.
  • Backward-compatible bug fix only: increment PATCH.
  • 0.y.z is initial development and may change at any time. Follow a project's documented pre-1.0 policy; do not invent one and call it a SemVer rule.
  • Never modify an artifact after its version has been released.
  • Normal versions are X.Y.Z, use non-negative integers, and have no leading zeroes.
  • Pre-releases rank below the associated normal version. Compare numeric identifiers numerically, non-numeric identifiers lexically in ASCII, and numeric identifiers below non-numeric ones.
  • Ignore build metadata when comparing precedence.

Inspect the public API and actual changes before recommending a version. Lead with the minimum safe version or bump and briefly cite the compatibility evidence. Use the bundled semver and semver-review skills for detailed work.

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. 2d ago First seen · 24 lines · 274 tokens per session scan A 5d7b3637b033

Subscribe to this mod's changes

semver-plugin AGENTS.md is an instructions file published in the GitHub repository LenoSeibert/semver-plugin (1 stars, last pushed 1mo ago), licensed MIT. It adds 274 tokens to every session, about $0.0014 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.

Related

Other instructions, from other repositories

coral CLAUDE.md

Instructions for cdknorow/coral, covering claude.md - coral go, mission, testing, go unit tests and legacy parity tools (historical reference).

cdknorow/coral · 1,898 tokens

pingfusi CLAUDE.md

Instructions for alex-durango/pingfusi: This repository is the released form of the pingfusi kit (published to npm as pingfusi). Releases are assembled and verified by the maintainers' release tooling, so commits here are release-granular and PRs cannot be merged directly — open an issue or PR and a maintainer ports…

alex-durango/pingfusi · 182 tokens

Circus-Chief CLAUDE.md

Instructions for ferrislucas/Circus-Chief, covering claude.md, project overview, common commands, development - start both frontend and backend and run all unit tests.

ferrislucas/Circus-Chief · 2,092 tokens

obsidian-llm-hub AGENTS.md

Instructions for takeshy/obsidian-llm-hub, a project described as: Obsidian plugin for AI chat, workflow automation, and semantic search — supports Gemini, OpenAI, OpenRouter, Grok, Ollama, and CLI backends.

takeshy/obsidian-llm-hub · 44 tokens

deva AGENTS.md

Instructions for thevibeworks/deva: Repo guidance for coding agents lives in CLAUDE.md (architecture, issue-based development workflow) and workflows/ (issue, commit, PR, release conventions). Read those before changing anything.

thevibeworks/deva · 92 tokens

cupcake CLAUDE.md

Instructions for eqtylab/cupcake, covering cupcake system overview, policy engine (wasm/rego) details, 1. routing vs. policy execution (critical), 2. opa rego v1 migration (critical) and 3. decisions & synthesis.

eqtylab/cupcake · 855 tokens