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/gustavobarbosab/sage/copilot-instructionsgit clone --depth 1 https://github.com/gustavobarbosab/sageWrote 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/gustavobarbosab/sage/copilot-instructions)<a href="https://agentmods.dev/instructions/gustavobarbosab/sage/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/gustavobarbosab/sage/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 | $0.00830 | $0.00830 |
| Opus 5 | $0.00415 | $0.00415 |
| Sonnet 5 | $0.00166 | $0.00166 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
sage 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 5d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SAGE — GitHub Copilot Instructions
Save this file as .github/copilot-instructions.md in your project root.
Copilot will use these instructions for all chat interactions in this repo.
Project Harness
Stack: Conventions: Avoid:
SAGE Workflow
SAGE is a spec-first, AI-assisted development workflow built on SDD, BDD, and Harness Engineering.
When I reference a SAGE command, follow the instructions below exactly.
/sage spec
Two-phase command — do NOT generate files immediately.
Phase 1 — Interview: Analyze the description and prepare questions. Show ALL questions at once:
I have X questions before writing your spec and behavior files. Answer them all and I'll generate both at once.
Question 1 of X
[Category: Purpose & scope]
<question>
Question 2 of X
[Category: Inputs & outputs]
<question>
...
Minimum 3, maximum 10 questions. Wait for answers before proceeding.
Phase 2 — Generation (after answers received):
Generate spec.md:
## Feature / ### What it does / ### Inputs / ### Outputs / ### Acceptance criteria / ### Do NOT
Then immediately generate behavior.md in the same response:
- Open Questions first (
- [ ]items or- No open questions.) - Test Cases (placeholder if questions remain, full BDD scenarios if none)
/sage behavior
Read spec.md. Generate behavior.md with:
Open Questions section (ALWAYS first):
- List every ambiguity as
- [ ] <question> - If no ambiguities:
- No open questions.
Test Cases section:
- Output
> ⚠️ Pending resolution of open questions above. - STOP. Wait for user to resolve questions.
After resolution: generate BDD Given/When/Then scenarios. Each scenario needs:
**Scenario: <title>**
Short → <condition + action + outcome>
Full:
- Given <precondition>
- When <action>
- Then <outcome>
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.
- 5d ago First seen · 123 lines · 830 tokens per session scan A 475a2643d969
sage copilot-instructions.md is an instructions file published in the GitHub repository gustavobarbosab/sage (2 stars, last pushed 2mo ago), licensed MIT. It adds 830 tokens to every session, about $0.0042 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).
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.
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 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).