Borrowing it
Nothing to install: this file belongs to gosha70/code-copilot-team. 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/gosha70/code-copilot-team/master/adapters/github-copilot/.github/instructions/stack-constraints.instructions.mdgit clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote 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/gosha70/code-copilot-team/stack-constraints)<a href="https://agentmods.dev/instructions/gosha70/code-copilot-team/stack-constraints"><img src="https://agentmods.dev/badge/instructions/gosha70/code-copilot-team/stack-constraints.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.00478 | $0.00478 |
| Opus 5 | $0.00239 | $0.00239 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
code-copilot-team stack-constraints.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 4d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stack Constraints
Rules for managing dependency versions and technology choices across all project types.
Version Pinning Policy
When starting a new project, prefer stable, well-documented versions over bleeding-edge:
- ORM / database tools — use latest stable, not pre-release (e.g., avoid beta/canary/rc).
- Framework — use LTS or latest stable release.
- Language runtime — use latest stable (not beta/rc).
- UI libraries — use latest stable release.
Check package documentation for "stable" vs "experimental" badges before adopting.
Dependency Installation Protocol
When agents create code requiring new packages:
- Agents should install dependencies as part of their task — if they have Bash permission, they must install what they import.
- If an agent lacks permission, pause and instruct the user to install manually before continuing.
- Always test the build after new dependencies — run the dev server, not just the type checker. Static analysis doesn't catch missing runtime packages.
- Check for peer dependency warnings — these often surface as runtime crashes, not compile errors.
When to Downgrade
Downgrade from a newer version to a stable one when:
- CLI or build tooling breaks (common with major version bumps of ORMs, bundlers, and frameworks).
- Runtime behavior changes unexpectedly from documented behavior.
- Community plugins/extensions don't yet support the new version.
- Error messages reference features marked "experimental" or "early access."
Document the version pin and the reason in the project CLAUDE.md or a DECISIONS.md so future contributors know why.
Stack-Specific Notes
Add version constraints relevant to your project in the project-level CLAUDE.md. For example:
## Stack Constraints
- ORM: Prisma 6.x (7.x has breaking CLI changes as of Feb 2026)
- Runtime: Node 20 LTS (not 22 — some deps don't support it yet)
- Framework: Next.js 14 stable (not 15 canary)
This keeps global rules generic while allowing each project to pin its own versions.
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.
- 4d ago First seen · 53 lines · 478 tokens per session scan A bdeffaa261d7
code-copilot-team stack-constraints.instructions.md is an instructions file published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed yesterday), licensed MIT. It adds 478 tokens to every session, about $0.0024 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
vibe-coding-prompt-template backend.instructions.md
Instructions for KhazP/vibe-coding-prompt-template: Read AGENTS.md, agentdocs/techstack.md, and agentdocs/codepatterns.md.
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).