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/workflow-optimization.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/workflow-optimization)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/workflow-optimization"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/workflow-optimization.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.00707 | $0.00707 |
| Opus 5 | $0.00353 | $0.00353 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
copilot-instructions workflow-optimization.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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Breakdown
Split large tasks into manageable steps; avoid hard token limits; split by functional domain when possible.
Planning and Routing
- For non-trivial work, route first and then follow
instructions/subagent-planning-workflow.instructions.md. - Treat
planning/README.md,planning/active/, andplanning/completed/as the versioned planning workspace. - Keep the context pack minimal, but do not omit mandatory instruction files or the planning workflow when the task needs staging.
Prioritization
- Critical config changes first
- Core validation logic second
- Template updates third
- Docs fourth
- Validation tests last
- Respect logical dependencies
Separation of Concerns
Keep single instruction files concise; group related files by domain; handle cross-cutting changes by layer (config, validation, templates); implement new features in phases (creation, integration, testing).
Context Preservation
Include relevant context gathering; avoid repeating already provided information; focus on requested specific changes; use targeted file searches when necessary.
Token Efficiency
- Avoid reproducing entire files
- Use comments to represent existing code when allowed
- Focus on minimal diffs
- Consolidate related changes
- Separate independent concerns
- Eliminate redundancies
- Never repeat provided context
- Focus exclusively on deltas
- Minimal examples
- Prioritize clarity over verbosity
- Target duplicated output and repeated narration before attempting any input/context reduction
- Never cut required working context by default just to save tokens; do that only with explicit proof that quality is preserved
Context Economy and Checkpoint
Full protocol, compression triggers, six-block state model, CHECKPOINT format, and user commands: instructions/context-economy-checkpoint.instructions.md.
User commands: checkpoint, compress context, update plan, show status, show progress, resume from summary (PT-BR aliases in .github/COMMANDS.md).
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 · 79 lines · 707 tokens per session scan A 2883e7139168
copilot-instructions workflow-optimization.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 707 tokens to every session, about $0.0035 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
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).
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.
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).
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.