custom_github_copilot_agent_builder memory-bank.instructions.md

custom_github_copilot_agent_builder memory-bank.instructions.md is an instructions file for GitHub Copilot from dhar174/custom_github_copilot_agent_builder. It costs 2,327 tokens per session, scanned A, original, MIT.

Instructions for keeping a project memory bank: Markdown files that record goals, design decisions, technical details, current work, and progress.

In plain words
What is it for?
Use it to organize project notes and require the assistant to read them before starting work.
Why use it?
It gives an AI coding assistant project context between sessions, so it can recover important information after its conversation memory is cleared.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot chat mode or prompt.

Install

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.

agentmods
npx agentmods add instructions/dhar174/custom_github_copilot_agent_builder/memory-bank
Clone the repo
git clone --depth 1 https://github.com/dhar174/custom_github_copilot_agent_builder

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 custom_github_copilot_agent_builder memory-bank.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dhar174/custom_github_copilot_agent_builder/memory-bank.svg)](https://agentmods.dev/instructions/dhar174/custom_github_copilot_agent_builder/memory-bank)
Your own site
<a href="https://agentmods.dev/instructions/dhar174/custom_github_copilot_agent_builder/memory-bank"><img src="https://agentmods.dev/badge/instructions/dhar174/custom_github_copilot_agent_builder/memory-bank.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,327 This file is loaded in full into every session.
When invoked 2,327 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.02327 $0.02327
Opus 5 $0.01163 $0.01163
Sonnet 5 $0.00465 $0.00465
Haiku 4.5 $0.00233 $0.00233

Measured 2d ago against content hash 8d6b774a6e47, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

custom_github_copilot_agent_builder memory-bank.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 2d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

.github/instructions/memory-bank.instructions.md · 299 lines

How it starts

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

Coding standards, domain knowledge, and preferences that AI should follow.

Memory Bank

You are an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task - this is not optional.

Memory Bank Structure

The Memory Bank consists of required core files and optional context files, all in Markdown format. Files build upon each other in a clear hierarchy:

flowchart TD
    PB[projectbrief.md] --> PC[productContext.md]
    PB --> SP[systemPatterns.md]
    PB --> TC[techContext.md]
    
    PC --> AC[activeContext.md]
    SP --> AC
    TC --> AC
    
    AC --> P[progress.md]
    AC --> TF[tasks/ folder]

Core Files (Required)

  1. projectbrief.md

    • Foundation document that shapes all other files
    • Created at project start if it doesn't exist
    • Defines core requirements and goals
    • Source of truth for project scope
  2. productContext.md

    • Why this project exists
    • Problems it solves
    • How it should work
    • User experience goals
  3. activeContext.md

    • Current work focus
    • Recent changes
    • Next steps
    • Active decisions and considerations
  4. systemPatterns.md

    • System architecture
    • Key technical decisions
    • Design patterns in use
    • Component relationships
  5. techContext.md

    • Technologies used
    • Development setup
    • Technical constraints
    • Dependencies
  6. progress.md

    • What works
    • What's left to build
    • Current status
    • Known issues
  7. tasks/ folder

    • Contains individual markdown files for each task
    • Each task has its own dedicated file with format TASKID-taskname.md
    • Includes task index file (_index.md) listing all tasks with their statuses
    • Preserves complete thought process and history for each task

Read the full file on GitHub · 299 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. 2d ago First seen · 299 lines · 2,327 tokens per session scan A 8d6b774a6e47

Subscribe to this mod's changes

custom_github_copilot_agent_builder memory-bank.instructions.md is an instructions file published in the GitHub repository dhar174/custom_github_copilot_agent_builder (7 stars, last pushed 7mo ago), licensed MIT. It adds 2,327 tokens to every session, about $0.0116 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-09-03.