do-not-create-agents-in-install-upgrade-or-background

do-not-create-agents-in-install-upgrade-or-background is an agent for coding agents from microsoft/BCQuality. It costs 0 tokens per session (297 once invoked), scanned A, original, MIT.

A rule that agent instances must be created during an interactive user session. Install, upgrade, job-queue, and scheduled background sessions cannot create them.

In plain words
What is it for?
Use it when designing setup pages or wizards that create and activate agents after an administrator opens the client.
Why use it?
It prevents runtime failures caused by trying to activate agents during app installation, upgrades, or background processing.

Agent

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/do-not-create-agents-in-install-upgrade-or-background
Clone the repo
git clone --depth 1 https://github.com/microsoft/BCQuality

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 do-not-create-agents-in-install-upgrade-or-background

README.md
[![agentmods](https://agentmods.dev/badge/agents/microsoft/bcquality/do-not-create-agents-in-install-upgrade-or-background.svg)](https://agentmods.dev/agents/microsoft/bcquality/do-not-create-agents-in-install-upgrade-or-background)
Your own site
<a href="https://agentmods.dev/agents/microsoft/bcquality/do-not-create-agents-in-install-upgrade-or-background"><img src="https://agentmods.dev/badge/agents/microsoft/bcquality/do-not-create-agents-in-install-upgrade-or-background.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 297 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.00297
Opus 5 $0.00000 $0.00148
Sonnet 5 $0.00000 $0.00059
Haiku 4.5 $0.00000 $0.00030

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

Security

Grade A, and why

do-not-create-agents-in-install-upgrade-or-background 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/do-not-create-agents-in-install-upgrade-or-background.md · 27 lines

What it actually says

Do not create agent instances from install, upgrade, or background sessions

Description

Agent.Create requires an interactive user session. The platform blocks creation from install codeunits, upgrade codeunits, and background sessions (job queue, scheduled tasks). Packaging an agent in an app does not mean spinning up instances at install. Models still call Create from OnInstallAppPerCompany to activate the agent.

Best Practice

Create instances from a setup page, a wizard, or another UI-driven path after the user is in a client session. Apply instructions and Activate there. For existing companies after an upgrade, document that an admin must open setup; do not create from the upgrade codeunit.

See sample: do-not-create-agents-in-install-upgrade-or-background.good.al.

Anti Pattern

Agent.Create inside OnInstallAppPerCompany, OnUpgradePerCompany, or a job-queue codeunit. The call fails at runtime even if it compiles. Detection signal: Agent.Create in Subtype = Install, Subtype = Upgrade, or a non-UI session.

See sample: do-not-create-agents-in-install-upgrade-or-background.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 a451f0255a5e

Subscribe to this mod's changes

do-not-create-agents-in-install-upgrade-or-background 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 297 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.