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/boecht/birre/edit-changeloggit clone --depth 1 https://github.com/boecht/birreWrote 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/boecht/birre/edit-changelog)<a href="https://agentmods.dev/instructions/boecht/birre/edit-changelog"><img src="https://agentmods.dev/badge/instructions/boecht/birre/edit-changelog.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.01607 | $0.01607 |
| Opus 5 | $0.00804 | $0.00804 |
| Sonnet 5 | $0.00321 | $0.00321 |
| Haiku 4.5 | $0.00161 | $0.00161 |
Grade A, and why
Changelog-Instructions 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CHANGELOG Standards for BiRRe (Authoring Instructions)
This is the authoritative guidance for creating or editing CHANGELOG.md.
⚠️ Critical Rules (Most Commonly Violated)
These rules are NON-NEGOTIABLE. Entries violating these will be rejected:
-
Comprehensive Coverage: The changelog entry MUST cover ALL commits on the current branch since the lastrelease/merge to main, not just the most recent commit.
- ✅ Correct: Analyze all 51 commits and extract user-facing changes from each
- ❌ Wrong: Only look at the last commit and write 5 lines
-
Category Order: Use categories in this EXACT order (omit empty ones):
- Changed
- Added
- Deprecated
- Removed
- Fixed
- Security
-
Imperative Mood: ALL bullets must use imperative verbs:
- ✅ Correct: "Add feature", "Fix bug", "Remove deprecated API", "Enhance performance"
- ❌ Wrong: "Added feature", "Fixed bug", "New feature", "Performance enhanced"
- ❌ Wrong: "Feature addition", "Bug fix", "Deprecated API removal"
-
User Benefits Over Implementation: Describe WHAT users get, not HOW you built it:
- ✅ Correct: "Improve startup time by 50%"
- ❌ Wrong: "Refactor config loader to use lazy loading"
Core Principles
- Changelogs are for humans, not machines — write clearly and concisely.
- Focus on user benefits, not technical implementation — describe impact, not code changes.
- Highlight up to three changes with biggest functional or user impact with
**TOP:**prefix. - Breaking changes are normal — make them highly visible with
**Breaking:**prefix. - Quality over backwards compatibility — don’t sugarcoat necessary changes.
Format Standards
File Structure
# Changelog
All notable changes to BiRRe (BitSight Rating Retriever) will be documented in this file.
See [Changelog Instructions](.github/instructions/edit-changelog.instructions.md) for updating guidelines.
## [X.Y.Z] - YYYY-MM-DD
### Changed
-
### Added
-
### Deprecated
-
### Removed
-
### Fixed
-
### Security
-
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.
- 5d ago First seen · 218 lines · 1,607 tokens per session scan A a83220dc23f0
Changelog-Instructions is an instructions file published in the GitHub repository boecht/birre (2 stars, last pushed 5d ago), licensed Unlicense. It adds 1,607 tokens to every session, about $0.0080 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
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).