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/tikoci/rosetta/manual-version-bumpgit clone --depth 1 https://github.com/tikoci/rosettaWhat 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.00323 | $0.00323 |
| Opus 5 | $0.00161 | $0.00161 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
rosetta manual-version-bump.instructions.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 3d 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
Manual version bump, on every channel
release.yml has no job that bumps package.json's version or promotes CHANGELOG.md's [Unreleased] heading — the old bump-version job (blind PATCH + 1, auto-committed to main) was removed because it couldn't reason across the latest/alpha/beta/rc channels.
- Do not add back a CI step that writes
package.json'sversionfield or editsCHANGELOG.mdand commits/pushes the result. Every version bump, on every channel, is a deliberate human edit before dispatchingRelease. - The workspace-only rewrite in "Determine npm release channel" (appending
$GITHUB_RUN_NUMBERto a prerelease version) is not an exception to this rule — it is never committed, exists only for the duration of the run, and does not touchCHANGELOG.md. - The backstops for a forgotten bump are the existing npm preflight ("already published" check) and the "Verify CHANGELOG promotion for latest-channel release" step — both fail loudly. Keep failures loud; do not paper over a missing bump by falling back to auto-generating one in CI.
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.
- 3d ago First seen · 12 lines · 323 tokens per session scan A 7e9a5cd4bdbc
rosetta manual-version-bump.instructions.md is an instructions file published in the GitHub repository tikoci/rosetta (43 stars, last pushed 17d ago), licensed MIT. It adds 323 tokens to every session, about $0.0016 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-30.
Other instructions, from other repositories
bun-mcp copilot-instructions.md
Copilot instructions for TomasHubelbauer/bun-mcp, covering github copilot instructions for the bun-mcp repository and formatting.
memorix GEMINI.md
Instructions for AVIDS2/memorix, covering memorix - cross-agent memory rules, session start - bind project, then load context, during session - capture important context, architecture & decisions and bug fixes & problem solving.
opencode-swarm copilot-instructions.md
Instructions for ZaxbyHub/opencode-swarm, covering mandatory pr publication protocol, pr title requirements, pr body requirements, validation requirements and release fragment requirement.
drift drift-release-mandatory.instructions.md
Nutze diese Kurz-Instruction, wenn schnell geklaert werden muss, ob im Drift-Repo ein manueller Release-Befehl noetig ist. Kurzregel: Conventional Commits verwenden, Release macht CI.
plan-forge release-checklist.instructions.md
Plan Forge release procedure — auto-loads when editing release-related files. Maintainer-only; NOT shipped to consuming projects.
progi AGENTS.md
Instructions for zseta/progi, covering agents.md, what this is, the one rule, layout and frontend / ui components.