Borrowing it
Nothing to install: this file belongs to ThiagoGuislotti/copilot-instructions. 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/ThiagoGuislotti/copilot-instructions/main/.github/instructions/super-agent.instructions.mdgit clone --depth 1 https://github.com/ThiagoGuislotti/copilot-instructionsWrote 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/thiagoguislotti/copilot-instructions/super-agent)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/super-agent"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/super-agent.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.02179 | $0.02179 |
| Opus 5 | $0.01090 | $0.01090 |
| Sonnet 5 | $0.00436 | $0.00436 |
| Haiku 4.5 | $0.00218 | $0.00218 |
Grade A, and why
copilot-instructions super-agent.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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Super Agent Lifecycle
Purpose
- Normalize all change-bearing work through one Super Agent lifecycle before implementation starts.
- Ensure planning, routing, specialist selection, testing, review, closeout, and planning-state updates happen in a fixed order.
- Prevent silent skipping of skills, instructions, or validation stages.
- Provide a workspace-safe bootstrap controller that can operate in both repository-adapter mode and global-runtime mode without making external skills or unrelated repositories the source of truth.
- Keep user-facing orchestration output concise by default without hiding failures, validation state, or operator decisions.
Scope
- Apply this lifecycle to any task that changes code, scripts, instructions, docs, runtime assets, workspace settings, pipelines, or repository governance.
- Purely informational answers with no intended file or runtime change may stay lightweight, but must still respect global routing and context rules.
- When the workspace exposes local
.githubadapter files, use the workspace-owned operating model and planning surfaces. - When the workspace does not expose those files, stay in global-runtime mode and use
.build/super-agent/for transient planning/spec artifacts.
Hard Rule
- Do not jump directly from user request to implementation.
- The Super Agent flow owns intake, normalization, spec registration for non-trivial change-bearing work, planning registration, specialist selection, execution strategy, validation, closeout, and planning-state updates.
- In Codex, prefer the repo-owned
super-agentskill as the bootstrap controller whenever skill discovery can activate it. - In Copilot, enforce the same lifecycle through this instruction and the mandatory routing flow because Copilot does not execute local skills directly.
- Do not assume
instruction-routing.catalog.yml,planning/, orinstructions/repository-operating-model.instructions.mdbelong to an arbitrary client repo unless that repo actually provides them.
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 · 138 lines · 2,179 tokens per session scan A 63cc74096af8
copilot-instructions super-agent.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 2,179 tokens to every session, about $0.0109 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-09-03.
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.