reapply-resource-instructions-on-upgrade

reapply-resource-instructions-on-upgrade is an agent for Claude Code from microsoft/BCQuality. It costs 0 tokens per session (248 once invoked), scanned A, original, MIT.

An upgrade pattern that reapplies an instruction resource to existing agent instances. Changing a bundled instruction file alone does not change instructions already copied onto running instances.

In plain words
What is it for?
Use it in upgrade code when a new app version changes the instruction resource for existing agents.
Why use it?
It prevents older agent instances from continuing to use outdated instructions after an app upgrade.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

About the project

microsoft/BCQuality is a structured knowledge base and skills library for Microsoft Business Central development. It records Business Central-specific rules and platform behaviors that coding agents or developers might otherwise get wrong. The catalogue entries provide the agents and skill that consume this guidance.

microsoft/BCQuality · 206 stars · on GitHub

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 agents/microsoft/bcquality/reapply-resource-instructions-on-upgrade
Clone the repo
git clone --depth 1 https://github.com/microsoft/BCQuality

Made for: Claude Code.

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 reapply-resource-instructions-on-upgrade

README.md
[![agentmods](https://agentmods.dev/badge/agents/microsoft/bcquality/reapply-resource-instructions-on-upgrade.svg)](https://agentmods.dev/agents/microsoft/bcquality/reapply-resource-instructions-on-upgrade)
Your own site
<a href="https://agentmods.dev/agents/microsoft/bcquality/reapply-resource-instructions-on-upgrade"><img src="https://agentmods.dev/badge/agents/microsoft/bcquality/reapply-resource-instructions-on-upgrade.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 248 The whole file, excluding the scripts and references it only reads on demand.
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.00000 $0.00248
Opus 5 $0.00000 $0.00124
Sonnet 5 $0.00000 $0.00050
Haiku 4.5 $0.00000 $0.00025

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

Security

Grade A, and why

reapply-resource-instructions-on-upgrade 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.

community/knowledge/agents/reapply-resource-instructions-on-upgrade.md · 27 lines

What it actually says

Reapply resource instructions to existing agent instances on upgrade

Description

Static instructions stored as an app resource are copied onto an instance only when you call SetInstructions. Shipping a new Instructions.txt in version 2.0 does not update agents created under 1.0. Models change the resource and assume running instances pick it up.

Best Practice

In the upgrade codeunit, find existing instances of your metadata provider and call SetInstructions again with NavApp.GetResourceAsText. Guard with an upgrade tag so the rewrite runs once per version that changes the file.

See sample: reapply-resource-instructions-on-upgrade.good.al.

Anti Pattern

Editing only the resource file, or calling SetInstructions solely from the first-time setup path. Detection signal: instruction resource in resourceFolders with no upgrade procedure that re-applies it.

See sample: reapply-resource-instructions-on-upgrade.bad.al.

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 · 27 lines · 0 tokens per session scan A 1c2b69818146

Subscribe to this mod's changes

reapply-resource-instructions-on-upgrade is an agent published in the GitHub repository microsoft/BCQuality (206 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 tokens. 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.