custom_github_copilot_agent_builder: Instructions file for GitHub Copilot

.github/instructions/update-docs-on-code-change.instructions.md

custom_github_copilot_agent_builder update-docs-on-code-change.instructions.md is an instructions file for GitHub Copilot from dhar174/custom_github_copilot_agent_builder. It costs 3,697 tokens per session, scanned A, original, MIT.

An instruction set that checks whether README files and other documentation need updating after application code changes.

In plain words
What is it for?
Keeping README files, API references, configuration guides, and related documentation aligned with code changes.
Why use it?
It helps prevent documentation from describing an older version of the software.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

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

Reuse

Borrowing it

Nothing to install: this file belongs to dhar174/custom_github_copilot_agent_builder. 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/dhar174/custom_github_copilot_agent_builder/main/.github/instructions/update-docs-on-code-change.instructions.md
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 update-docs-on-code-change.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/dhar174/custom_github_copilot_agent_builder/update-docs-on-code-change.svg)](https://agentmods.dev/instructions/dhar174/custom_github_copilot_agent_builder/update-docs-on-code-change)
Your own site
<a href="https://agentmods.dev/instructions/dhar174/custom_github_copilot_agent_builder/update-docs-on-code-change"><img src="https://agentmods.dev/badge/instructions/dhar174/custom_github_copilot_agent_builder/update-docs-on-code-change.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,697 This file is loaded in full into every session.
When invoked 3,697 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.03697 $0.03697
Opus 5 $0.01849 $0.01849
Sonnet 5 $0.00739 $0.00739
Haiku 4.5 $0.00370 $0.00370

Measured 3d ago against content hash 159ee49a9b6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

custom_github_copilot_agent_builder update-docs-on-code-change.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 3d 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

1 near-identical copy found in the catalogue:

.github/instructions/update-docs-on-code-change.instructions.md · 550 lines

How it starts

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

Update Documentation on Code Change

Overview

Ensure documentation stays synchronized with code changes by automatically detecting when README.md, API documentation, configuration guides, and other documentation files need updates based on code modifications.

Instruction Sections and Configuration

The following parts of this section, Instruction Sections and Configurable Instruction Sections and Instruction Configuration are only relevant to THIS instruction file, and are meant to be a method to easily modify how the Copilot instructions are implemented. Essentially the two parts are meant to turn portions or sections of the actual Copilot instructions on or off, and allow for custom cases and conditions for when and how to implement certain sections of this document.

Instruction Sections and Configurable Instruction Sections

There are several instruction sections in this document. The start of an instruction section is indicated by a level two header. Call this an INSTRUCTION SECTION. Some instruction sections are configurable. Some are not configurable and will always be used.

Instruction sections that ARE configurable are not required, and are subject to additional context and/or conditions. Call these CONFIGURABLE INSTRUCTION SECTIONS.

Configurable instruction sections will have the section's configuration property appended to the level two header, wrapped in backticks (e.g., apply-this). Call this the CONFIGURABLE PROPERTY.

The configurable property will be declared and defined in the Instruction Configuration portion of this section. They are booleans. If true, then apply, utilize, and/or follow the instructions in that section.

Each configurable instruction section will also have a sentence that follows the section's level two header with the section's configuration details. Call this the CONFIGURATION DETAIL.

The configuration detail is a subset of rules that expand upon the configurable instruction section. This allows for custom cases and/or conditions to be checked that will determine the final implementation for that configurable instruction section.

Read the full file on GitHub · 550 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. 3d ago First seen · 550 lines · 3,697 tokens per session scan A 159ee49a9b6b

Subscribe to this mod's changes

custom_github_copilot_agent_builder update-docs-on-code-change.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 3,697 tokens to every session, about $0.0185 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.

Related

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.

openai/codex · 5,182 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 · 6,785 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,296 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,469 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens