Borrowing it
Nothing to install: this file belongs to tikoci/rosetta. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/tikoci/rosetta/main/.github/instructions/changelog-discipline.instructions.mdgit clone --depth 1 https://github.com/tikoci/rosettaWrote 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.
[](https://agentmods.dev/instructions/tikoci/rosetta/changelog-discipline)<a href="https://agentmods.dev/instructions/tikoci/rosetta/changelog-discipline"><img src="https://agentmods.dev/badge/instructions/tikoci/rosetta/changelog-discipline.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00368 | $0.00368 |
| Opus 5 | $0.00184 | $0.00184 |
| Sonnet 5 | $0.00074 | $0.00074 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
rosetta changelog-discipline.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 7d 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
Changelog discipline
If a change alters behavior users or operators can notice — CLI flags, MCP tool shape, DB schema, install/update flow, release/CI behavior, documented invariants — add one bullet under CHANGELOG.md → [Unreleased] in the same PR.
- Use the smallest accurate section:
Added,Changed,Fixed,Removed,Deprecated, orSecurity. - One bullet per behavior change. Do not log pure refactors, test churn, or CI-only auto-bumps with no external effect.
CHANGELOG.mdcaptures what shipped. Put rationale inDESIGN.mdand future work inBACKLOG.md.
When promoting [Unreleased] to a version heading for a release, also update the reference-style link definitions at the bottom of the file: add [<version>]: <repo>/compare/v<previous>...v<version> and update [Unreleased] to compare from compare/v<version>...HEAD. The headings are reference links, so a promotion without its definition renders as literal brackets and leaves [Unreleased] comparing from the previous release. No automated check catches this — the release gate only greps for the heading, and markdownlint's MD051 checks heading anchors, not undefined reference links. See MANUAL.md → "Version bumps are a manual step".
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.
- 7d ago First seen · 14 lines · 368 tokens per session scan A 10f4bfaf2578
rosetta changelog-discipline.instructions.md is an instructions file published in the GitHub repository tikoci/rosetta (44 stars, last pushed today), licensed MIT. It adds 368 tokens to every session, about $0.0018 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
plan-forge version.instructions.md
Version management — Semantic versioning, auto-increment, commit-driven version bumps, release tagging.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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).
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.
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).