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/burly-mingo/modernization-kit/copilot-instructionsgit clone --depth 1 https://github.com/Burly-Mingo/modernization-kitWhat 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.01572 | $0.01572 |
| Opus 5 | $0.00786 | $0.00786 |
| Sonnet 5 | $0.00314 | $0.00314 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
modernization-kit copilot-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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application Modernization — Copilot Custom Instructions
Part of the Legacy Application Modernization Kit by Burly Mingo LLC
You are assisting with a legacy application modernization project. This workspace contains a structured, multi-phase methodology that produces real engineering deliverables through iterative collaboration between you and a human domain expert.
How to Use This
This methodology has 6 phases (0-5), each with a dedicated prompt file in .github/prompts/. Work through them in order:
- Open the prompt file for the current phase (e.g.,
@workspace /prompts/phase-0-discovery.prompt.md) - Follow the instructions in that prompt to produce the phase deliverable
- The human reviews and corrects your output
- Move to the next phase only after human approval
The prompt files contain the detailed requirements for each phase. These instructions provide the principles and constraints that apply across all phases.
Non-Negotiable Principles
-
Modernize, don't translate. Changing the language without rethinking the architecture is not modernization. Every legacy system has workflows that exist because of technical limitations that no longer apply. Find them. Fix them. Don't preserve them in a new language.
-
Containers by default, not by dogma. Recommend containerized, cloud-agnostic deployment as the default. But if the organization is committed to a specific cloud and cloud-native services genuinely simplify their life, that's valid. Ask, respect the answer, document the trade-off.
-
Buy vs. build at every decision point. For every component, ask: does a product (open source or commercial) do this better than we could build it? But know the audience — many enterprises require vendor support contracts, SLAs, and security attestations. Ask about open-source policy and procurement requirements early.
-
AI-assisted, spec-driven development is the baseline. Estimates assume an experienced developer/architect using an AI IDE with structured workflow. Not vibe coding. Without experience or structured specs, AI multiplies chaos. If traditional development is planned, multiply timelines by 2.5-4x.
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 · 87 lines · 1,572 tokens per session scan A 3b18cd048423
modernization-kit copilot-instructions.md is an instructions file published in the GitHub repository Burly-Mingo/modernization-kit (11 stars, last pushed 6mo ago), licensed MIT. It adds 1,572 tokens to every session, about $0.0079 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-30.
Other instructions, from other repositories
kirocc CLAUDE.md
Instructions for d-kuro/kirocc, covering agent guidelines, core principles, project overview, commands and code conventions.
kaiord CLAUDE.md
Instructions for pablo-albaladejo/kaiord, covering claude.md, project overview, commands, install and build and test.
nestjs-starter config.instructions.md
Instructions for hmake98/nestjs-starter: // src/app/config/redis.config.ts import { registerAs } from '@nestjs/config'.
nestjs-starter modules.instructions.md
Instructions for hmake98/nestjs-starter: @Module({ imports: [DatabaseModule], controllers: [PostPublicController, PostAdminController], providers: [PostService], exports: [PostService], }) export class PostModule {}.
kiro-gateway CLAUDE.md
Claude Code instructions for ankitcharolia/kiro-gateway, covering claude.md — guide for ai agents working in kiro gateway, what this project is, request path, file map and configuration.
pudo-code-system CLAUDE.md
Instructions for DongDuong2001/pudo-code-system, covering claude code instructions, required workflow, model-specific notes, claude fable 5 and repository references.