Borrowing it
Nothing to install: this file belongs to MaximilianMayr94/skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/MaximilianMayr94/skills/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/MaximilianMayr94/skillsWrote 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/maximilianmayr94/skills/copilot-instructions)<a href="https://agentmods.dev/instructions/maximilianmayr94/skills/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/maximilianmayr94/skills/copilot-instructions.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.1 | $0.01792 | $0.01792 |
| Opus 5 | $0.00896 | $0.00896 |
| Sonnet 5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade A, and why
skills 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 8d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
General Rules
- Communication can be nearly skipped as most of the information is in the documents.
- Keep the final answer to the minimum, do not explain anything just write notes what was done.
- files should be short and concise because they are processed by AI.
- Use bullet points instead of long paragraphs.
- Use mermaid diagrams as much as possible - pictures tell more than words
- Do not explain everything, expect professional knowledge. But always explain referenced tools / and libraries in one short sentence
- Reference content instead of writing it again
- For diagrams use "mermaid" in markdown
- Always ask for clarification if you are not sure about something. Do not make assumptions.
- Keep your answer short, communicate in the documents/files
Constraints
- Never change files outside of this repository
- Use git only for read-only actions
Software Development Lifecycle - SDLC
This project follows the VAgile process. It is a combination of the traditional V-Model and the Agile process. The macro part of the project (beginning and end) follows the V-Model, while the micro part (Refinement/Implementation/Review) follows an agile methodology. The V-Model parts aim to be slow and complete, while the AGILE part aims to be quick and should be seen as prototyping.
- Definition (V-Model - whole project): In this phase the project context and software requirements are defined.
context.md,software_requirements.mdare created. (init, brainstorm, criticize skill) - Architecture (V-Model - whole project): In this phase the
architecture.mdis defined and created fromcontext.mdandsoftware_requirements.md. Functions are grouped in components and interfaces are defined. (architect skill) - Refinement (Agile - part): In this phase the implementation/design of each *component is defined. For each component modules and units are defined. As well as data handling, interfaces and so on. So the code can be completely derived from these documents. Executed component for component. (refine, ticket_prep skill)
- Implementation (Agile - part): Tickets are implemented . (implement skill)
- Review (Agile - part): One slice is reviewed and feedback is given. The review document is created and updated. Problems, bugs, gaps and contradicting information are defined. Suggestions for improvements and changes to the architecture and refinement are given. (review skill)
- Verification (V-Model - whole project): The software is verified against
software_requirements.md,context.mdand the architecture. The verify document is created and updated. The final verification result is defined. (verify skill)
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.
- 8d ago First seen · 102 lines · 1,792 tokens per session scan A 3de9ba2539d2
skills copilot-instructions.md is an instructions file published in the GitHub repository MaximilianMayr94/skills (1 stars, last pushed 1mo ago), licensed MIT. It adds 1,792 tokens to every session, about $0.0090 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
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.