mnemonic: Instructions file for GitHub Copilot

.github/instructions/memory-files.instructions.md

mnemonic memory-files.instructions.md is an instructions file for GitHub Copilot from modeled-information-format/mnemonic. It costs 600 tokens per session, scanned A, original, MIT.

A set of rules for storing information in structured memory files. It defines required details such as an identifier, type, dates, title and tags, plus optional expiry and source information.

In plain words
What is it for?
Use it when creating files for facts, events or procedures that an agent should remember. It also supports recording when information is valid, how long it should last and where it came from.
Why use it?
It gives stored memories a consistent format, making them easier to identify, classify and update over time.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is modeled-information-format/mnemonic's own configuration. It tells GitHub Copilot how to work on mnemonic 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 mnemonic configures →

Reuse

Borrowing it

Nothing to install: this file belongs to modeled-information-format/mnemonic. 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/modeled-information-format/mnemonic/main/.github/instructions/memory-files.instructions.md
Clone the repo
git clone --depth 1 https://github.com/modeled-information-format/mnemonic

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 mnemonic memory-files.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/modeled-information-format/mnemonic/memory-files/github.svg)](https://agentmods.dev/instructions/modeled-information-format/mnemonic/memory-files)
Your own site
<a href="https://agentmods.dev/instructions/modeled-information-format/mnemonic/memory-files"><img src="https://agentmods.dev/badge/instructions/modeled-information-format/mnemonic/memory-files/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 mnemonic memory-files.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/modeled-information-format/mnemonic/memory-files"><img src="https://agentmods.dev/badge/instructions/modeled-information-format/mnemonic/memory-files.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 600 This file is loaded in full into every session.
When invoked 600 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.00600 $0.00600
Opus 5.5 $0.00240 $0.00240
Sonnet 5.5 $0.00120 $0.00120
Haiku 4.5 $0.00060 $0.00060

Measured 13d ago against content hash a4359f10d05b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

mnemonic memory-files.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 13d 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/memory-files.instructions.md · 81 lines

How it starts

The opening of the file, as written. The whole thing — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory File Guidelines (MIF 1.4.2 Level 3)

Concept frontmatter keys are camelCase (MIF 1.4.2 section 3.3). Legacy snake_case keys (valid_from, source_type, compressed_at) in older memories are still read; do not introduce them in new or edited files.

Required Frontmatter Fields

---
id: <uuid>                    # Unique identifier (uuidgen format)
type: semantic|episodic|procedural
namespace: {category}/user    # e.g., decisions/user, learnings/user
created: <ISO8601>            # Creation timestamp
modified: <ISO8601>           # Last modification timestamp
title: "Title"                # Human-readable title
tags: [tag1, tag2]            # Categorization tags
---

Optional Temporal Fields

temporal:
  validFrom: <ISO8601>       # When content became valid
  validUntil: <ISO8601>      # When content expires (optional)
  recordedAt: <ISO8601>      # When it was recorded
  decay:
    model: exponential        # Decay model type
    halfLife: P7D            # ISO 8601 duration
    strength: 0.85            # Current strength 0.0-1.0

Optional Provenance Fields

provenance:
  sourceType: user_explicit | user_implicit | agent_inferred | external_import | system_generated
  agent: model-identifier     # e.g., claude-opus-4
  confidence: 0.9             # Confidence score 0.0-1.0

Memory Types

  • semantic: Facts, decisions, specifications - things that ARE true
  • episodic: Events, debug sessions, incidents - things that HAPPENED
  • procedural: Workflows, patterns, how-tos - things you DO

Content Structure

After frontmatter, use standard Markdown:

  • H1 heading matching the title
  • Clear sections for context, details, implications
  • Code blocks with language specification
  • Links to related memories or external resources

Relationships

Relationships are authoritative in frontmatter and mirrored as Markdown links under ## Relationships (MIF 1.4.2 section 5.3):

relationships:
  - type: relates-to                 # kebab-case token, not relates_to
    target: urn:mif:<target-uuid>
    metadata:
      label: "Optional note"

Read the full file on GitHub · 81 lines

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. 13d ago Changed a4359f10d05b
  2. 14d ago Changed · +25 lines · +188 tokens per session aad3a1dec1be
  3. 1mo ago First seen · 56 lines · 412 tokens per session scan A d8526eb08b9b

Subscribe to this mod's changes

mnemonic memory-files.instructions.md is an instructions file published in the GitHub repository modeled-information-format/mnemonic (23 stars, last pushed 10d ago), licensed MIT. It adds 600 tokens to every session, about $0.0024 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

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,649 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,549 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

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens