Borrowing it
Nothing to install: this file belongs to shangyankeji/super-dev. 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/shangyankeji/super-dev/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/shangyankeji/super-devWrote 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/shangyankeji/super-dev/copilot-instructions)<a href="https://agentmods.dev/instructions/shangyankeji/super-dev/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/shangyankeji/super-dev/copilot-instructions/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.
<a href="https://agentmods.dev/instructions/shangyankeji/super-dev/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/shangyankeji/super-dev/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" 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.00828 | $0.00828 |
| Opus 5.5 | $0.00331 | $0.00331 |
| Sonnet 5.5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
super-dev 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 2mo 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Super Dev IDE Rules (vscode-copilot)
Positioning
- Super Dev is a host-level workflow governor, not an LLM platform.
- Keep using the host's model capabilities; do not expect extra model APIs from Super Dev.
- The host remains responsible for actual coding, tool execution, and file changes.
Runtime Contract
- Treat Super Dev as the local Python workflow tool plus this host rule file, not as a separate coding engine.
- When the user says
/super-dev ...,super-dev: ..., orsuper-dev：..., immediately enter the Super Dev pipeline. - Use host-native browse/search/web for research and host-native editing/terminal for implementation.
- Use local
super-devcommands when you need to generate or refresh documents, spec artifacts, quality reports, or delivery manifests.
First-Response Contract
- On the first reply after
/super-dev ...,super-dev: ..., orsuper-dev：..., explicitly state that Super Dev pipeline mode is now active rather than normal chat mode. - Before the first reply, read
.super-dev/WORKFLOW.mdandoutput/*-bootstrap.mdwhen present, and treat them as the explicit bootstrap contract for this repository. - The first reply must explicitly state that the current phase is
research, and that you will readknowledge/plusoutput/knowledge-cache/*-knowledge-bundle.jsonfirst when available before similar-product research. - The first reply must explicitly state the next sequence: research -> three core documents -> wait for user confirmation -> Spec / tasks -> frontend first with runtime verification -> backend / tests / delivery.
- The first reply must explicitly promise that you will stop after the three core documents and wait for approval before creating Spec or writing code.
Local Knowledge Contract
- Read relevant files under
knowledge/before drafting the three core documents. - If
output/knowledge-cache/*-knowledge-bundle.jsonexists, read it first and inherit its matched local knowledge into PRD, architecture, UIUX, Spec, and execution. - Treat local knowledge hits as hard project constraints, especially for standards, anti-patterns, checklists, and scenario packs.
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.
- 2mo ago First seen · 52 lines · 828 tokens per session scan A 905a536272b5
super-dev copilot-instructions.md is an instructions file published in the GitHub repository shangyankeji/super-dev (278 stars, last pushed 4mo ago), licensed MIT. It adds 828 tokens to every session, about $0.0033 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-08-30.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.