packmind: Instructions file for GitHub Copilot

.github/instructions/packmind-changelog.instructions.md

packmind packmind-changelog.instructions.md is an instructions file for GitHub Copilot from PackmindHub/packmind. It costs 215 tokens per session, scanned A, original, Apache-2.0.

A set of rules for maintaining a CHANGELOG.md file, a document that records what changed in each software release. It follows the Keep a Changelog format and uses dated release entries and comparison links.

In plain words
What is it for?
Use it when publishing a release or updating ongoing work. It guides version headings, ISO-formatted dates, an Unreleased section, and links between releases.
Why use it?
It prevents release notes from becoming inconsistent or incomplete. Developers can more easily see what changed between versions and what is still unreleased.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is PackmindHub/packmind's own configuration. It tells GitHub Copilot how to work on packmind itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything packmind configures →

Reuse

Borrowing it

Nothing to install: this file belongs to PackmindHub/packmind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/PackmindHub/packmind/main/.github/instructions/packmind-changelog.instructions.md
Clone the repo
git clone --depth 1 https://github.com/PackmindHub/packmind

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for packmind packmind-changelog.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/packmindhub/packmind/packmind-changelog/github.svg)](https://agentmods.dev/instructions/packmindhub/packmind/packmind-changelog)
Your own site
<a href="https://agentmods.dev/instructions/packmindhub/packmind/packmind-changelog"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/packmind-changelog/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for packmind packmind-changelog.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/packmindhub/packmind/packmind-changelog"><img src="https://agentmods.dev/badge/instructions/packmindhub/packmind/packmind-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 215 This file is loaded in full into every session.
When invoked 215 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00215 $0.00215
Opus 5.5 $0.00086 $0.00086
Sonnet 5.5 $0.00043 $0.00043
Haiku 4.5 $0.00021 $0.00021

Measured 1mo ago against content hash 09711d477bfc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

packmind packmind-changelog.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 1mo 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.

.github/instructions/packmind-changelog.instructions.md · 12 lines

What it actually says

Standard: Changelog

Maintain a consistent and well-structured CHANGELOG.MD file following the Keep a Changelog format to ensure all releases are properly documented with accurate version links and dates. This standard ap... :

  • An entry of the CHANGELOG should not exceed 200 characters
  • Ensure all released versions have their corresponding comparison links defined at the bottom of the CHANGELOG.MD file in the format [X.Y.Z]: https://github.com/PackmindHub/packmind/compare/release/...release/X.Y.Z
  • Format all release dates using the ISO 8601 date format YYYY-MM-DD (e.g., 2025-11-21) to ensure consistent and internationally recognized date representation
  • Maintain an [Unreleased] section at the top of the changelog with its corresponding link at the bottom pointing to HEAD to track ongoing changes between releases

Full standard is available here for further request: Changelog

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. 1mo ago Changed · +1 lines · +14 tokens per session 09711d477bfc
  2. 1mo ago First seen · 11 lines · 201 tokens per session scan A 57b68f9443b2

Subscribe to this mod's changes

packmind packmind-changelog.instructions.md is an instructions file published in the GitHub repository PackmindHub/packmind (319 stars, last pushed 4d ago), licensed Apache-2.0. It adds 215 tokens to every session, about $0.0009 per session on Opus 5.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.

Related

Other instructions, from other repositories

plan-forge version.instructions.md

Version management — Semantic versioning, auto-increment, commit-driven version bumps, release tagging.

srnichols/plan-forge · 1,404 tokens

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,786 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens