trainer-demo-deploy: Instructions file for GitHub Copilot

.github/instructions/templates-json.instructions.md

trainer-demo-deploy templates-json.instructions.md is an instructions file for GitHub Copilot from MicrosoftLearning/trainer-demo-deploy. It costs 1,536 tokens per session, scanned A, original, MIT.

A set of instructions for maintaining a catalogue of reusable project templates in a JSON file. JSON is a text format commonly used to store structured data.

In plain words
What is it for?
Use it when adding or updating template entries, including their descriptions, previews, authors, source repositories, tags, costs, and deployment times.
Why use it?
It defines the required fields, allowed tags, metadata sources, and validation rules so catalogue entries stay consistent.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

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

Reuse

Borrowing it

Nothing to install: this file belongs to MicrosoftLearning/trainer-demo-deploy. 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/MicrosoftLearning/trainer-demo-deploy/main/.github/instructions/templates-json.instructions.md
Clone the repo
git clone --depth 1 https://github.com/MicrosoftLearning/trainer-demo-deploy

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 trainer-demo-deploy templates-json.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/microsoftlearning/trainer-demo-deploy/templates-json/github.svg)](https://agentmods.dev/instructions/microsoftlearning/trainer-demo-deploy/templates-json)
Your own site
<a href="https://agentmods.dev/instructions/microsoftlearning/trainer-demo-deploy/templates-json"><img src="https://agentmods.dev/badge/instructions/microsoftlearning/trainer-demo-deploy/templates-json/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for trainer-demo-deploy templates-json.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/microsoftlearning/trainer-demo-deploy/templates-json"><img src="https://agentmods.dev/badge/instructions/microsoftlearning/trainer-demo-deploy/templates-json.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,536 This file is loaded in full into every session.
When invoked 1,536 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.01536 $0.01536
Opus 5.5 $0.00614 $0.00614
Sonnet 5.5 $0.00307 $0.00307
Haiku 4.5 $0.00154 $0.00154

Measured today against content hash 60de46b18a56, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

trainer-demo-deploy templates-json.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 today.

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.

.github/instructions/templates-json.instructions.md · 138 lines

How it starts

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

Templates Catalog Implementation Instructions

These instructions govern adding and maintaining entries in static/templates.json. They define a deterministic process and validation rules.

Scope

  • File: static/templates.json (single JSON array of template objects)
  • Tags: must be from src/data/tags.tsx TagType union
  • Sources: A single GitHub repository per entry is the authoritative source for metadata

Contract: Template Entry Schema

Fields and types:

  • title (string, required, unique)
  • description (string, required) - Omit reference to bicep or AZD, it is the demo that we care about
  • preview (string, required) — relative path under ./templates/images/ or an absolute HTTPS URL
  • website (string, required) — author profile or project page
  • author (string, required)
  • source (string, required) — GitHub repo URL
  • demoguide (string, optional) — raw markdown URL
  • tags (string[], required) — each value must be in TagType
  • industry (string, optional) — business vertical; omit for general-purpose templates
  • cost (string, required) — decimal as string (e.g., "3.00")
  • deploytime (string, required) — minutes as string (e.g., "5")
  • prereqs (string, optional) — raw markdown URL

Conventions:

  • Keep keys in the order listed above
  • All fields are JSON strings except tags (array of strings)
  • Missing industry values are normalized to General by the catalog
  • Deduplicate and sort tags lexicographically for stable diffs
  • No trailing commas; entire file must be a single valid JSON array

Allowed Tags

Authoritative allowed values are defined in src/data/tags.tsx (TagType). Do not invent new tags here—add to TagType first if necessary. Should contain a tag from the ILT course catalog.

Automation Workflow: From GitHub Repo to Entry

When a user provides a GitHub repository URL, populate fields as follows:

  1. Discover metadata
    • source: the provided repo URL
    • website: repo owner profile URL (e.g., https://github.com/) or the repo homepage if defined
    • author: repo owner display name if available; otherwise owner handle
    • title: prefer a concise productized name from README H1; else repo name in human case
    • description: first paragraph under README H1 (sanitize to one sentence, max ~240 chars)
    • demoguide: README raw URL if it serves as the demo guide, or search for demoguide/*.md, docs/guide.md; use raw URL
    • prereqs: search for prereqs.md or similar; use raw URL if present
    • preview: look for images referenced in README (png/svg/jpg/webp). Prefer a repo static/templates/images/ asset if already in our repo, else the first readable image in the repo via raw URL. If none, set ./templates/images/test.png.
    • industry: use a business vertical explicitly named in the README; otherwise omit it so the entry defaults to General

Read the full file on GitHub · 138 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. today First seen · 138 lines · 1,536 tokens per session scan A 60de46b18a56

Subscribe to this mod's changes

trainer-demo-deploy templates-json.instructions.md is an instructions file published in the GitHub repository MicrosoftLearning/trainer-demo-deploy (31 stars, last pushed 11d ago), licensed MIT. It adds 1,536 tokens to every session, about $0.0061 per session on Opus 5.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-11-07.

Related

trainer-demo-deploy templates-json.instructions.md compared with instructions from other repositories

trainer-demo-deploy templates-json.instructions.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
trainer-demo-deploy templates-json.instructions.mdMicrosoftLearning/trainer-demo-deployInstructions file3111d agoMITA1,536GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file275k3d agoMITA4,313Codex, OpenCode