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/ssdeanx/ssd-ai/update-docs-on-code-changegit clone --depth 1 https://github.com/ssdeanx/ssd-aiWrote 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/ssdeanx/ssd-ai/update-docs-on-code-change)<a href="https://agentmods.dev/instructions/ssdeanx/ssd-ai/update-docs-on-code-change"><img src="https://agentmods.dev/badge/instructions/ssdeanx/ssd-ai/update-docs-on-code-change.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 | $0.03697 | $0.03697 |
| Opus 5 | $0.01849 | $0.01849 |
| Sonnet 5 | $0.00739 | $0.00739 |
| Haiku 4.5 | $0.00370 | $0.00370 |
Grade A, and why
ssd-ai 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.
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.
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.
- 3d ago First seen · 550 lines · 3,697 tokens per session scan A 159ee49a9b6b
ssd-ai update-docs-on-code-change.instructions.md is an instructions file published in the GitHub repository ssdeanx/ssd-ai (3 stars, last pushed 8mo 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-08-31.
Other instructions, from other repositories
Genesis-World-MCP AGENTS.md
AGENTS.md instructions for Gnidreve/Genesis-World-MCP, covering agents.md — cas genesisworld mcp, what this is, standing orders — read first, design pillars and source layout & conventions.
atelier-mcp copilot-instructions.md
Copilot instructions for anshrajore/atelier-mcp, covering run npm run sync-adapters to update, universal ui/ux rules, universal backend architecture rules and framework presets (available in skills/atelier/presets/).
atelier-mcp CLAUDE.md
Claude Code instructions for anshrajore/atelier-mcp, covering atelier quality gate adapter for claude code (claude.md), run npm run sync-adapters to update, universal ui/ux rules, universal backend architecture rules and framework presets (available in skills/atelier/presets/).
atelier-mcp AGENTS.md
AGENTS.md instructions for anshrajore/atelier-mcp, covering atelier quality gate adapter for agents.md, run npm run sync-adapters to update, universal ui/ux rules, universal backend architecture rules and framework presets (available in skills/atelier/presets/).
mcpscore AGENTS.md
Instructions for mcp-box/mcpscore, covering agent instructions for mcpscore and gotchas (learned the hard way).
director CLAUDE.md
Claude Code instructions for fdmtl/director, covering claude.md, product overview and development workflow, quality standards and workflow, engineering excellence and library documentation lookup.