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/thiagoguislotti/copilot-instructions/brainstorm-spec-workflowgit 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/brainstorm-spec-workflow)<a href="https://agentmods.dev/instructions/thiagoguislotti/copilot-instructions/brainstorm-spec-workflow"><img src="https://agentmods.dev/badge/instructions/thiagoguislotti/copilot-instructions/brainstorm-spec-workflow.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.00834 | $0.00834 |
| Opus 5 | $0.00417 | $0.00417 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
copilot-instructions brainstorm-spec-workflow.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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Brainstorming And Specification Workflow
Purpose
- Introduce a brainstorming and specification step before implementation planning for non-trivial change-bearing work.
- Keep design intent, alternatives, risks, and acceptance criteria versioned separately from execution plans.
- Prevent implementation planning from becoming the first place where architectural decisions are made.
When A Spec Is Mandatory
Create or update a spec under planning/specs/active/ when the workspace provides that surface, otherwise under .build/super-agent/specs/active/, when any of these are true:
- the task introduces or changes behavior, architecture, workflow, or feature scope
- the task is non-trivial and planning is already required
- the task spans multiple work items and design tradeoffs must be documented first
- the request changes orchestration, runtime behavior, governance flow, or user-facing workflows
- the request is ambiguous enough that alternatives or explicit design decisions are needed before implementation planning
When A Spec Can Be Skipped
A separate spec is usually not required when all of these are true:
- the work is trivial and tightly scoped
- the task is maintenance-only, doc-only, title-only, or configuration-only
- there is no meaningful design tradeoff to lock down before planning
Spec Workspace Contract
- Use
planning/specs/README.mdas the guide for versioned specs when the workspace provides it. - Active specs live in
planning/specs/active/when the workspace provides a versioned spec surface; otherwise they live in.build/super-agent/specs/active/. - Completed specs move to
planning/specs/completed/or.build/super-agent/specs/completed/only when the associated workstream is materially finished. - Reuse the same spec file for the same workstream instead of creating duplicates.
- Use stable names such as
spec-<scope>.md.
Dating Policy (Mandatory)
- Every spec must include
Generated: YYYY-MM-DD HH:mmat the top. - Every key decision, alternative, or assumption added after creation must carry a
[YYYY-MM-DD HH:mm]prefix. - When planning readiness changes (e.g., spec updated after new information), append
Updated: YYYY-MM-DD HH:mm — <reason>to the planning readiness statement. - Dates allow agents resuming from a compacted context to read the spec and understand exactly when each design decision was made and whether it is still current.
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 · 61 lines · 834 tokens per session scan A 1cded6706b87
copilot-instructions brainstorm-spec-workflow.instructions.md is an instructions file published in the GitHub repository ThiagoGuislotti/copilot-instructions (2 stars, last pushed 2mo ago), licensed MIT. It adds 834 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
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.
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.
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).