What is moosestack copilot-instructions.md?

Repository instructions for Moose, a monorepo containing multiple related Rust, TypeScript, and Python projects in one code repository. It explains the repository layout, build commands, tests, linting, and development flow.

Use it when navigating the Moose repository, building its components, running Rust or JavaScript tests, checking code quality, running end-to-end tests, or preparing a commit.

It gives contributors the project-specific checks needed before committing changes. It also clarifies which tools and commands apply to each language and package area.

How 514-labs/moosestack configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to 514-labs/moosestack. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/514-labs/moosestack/main/.github/copilot-instructions.md

Clone the repo

git clone --depth 1 https://github.com/514-labs/moosestack

Made for: GitHub Copilot.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/514-labs/moosestack/copilot-instructions/github.svg)](https://agentmods.dev/instructions/514-labs/moosestack/copilot-instructions)

Your own site

<a href="https://agentmods.dev/instructions/514-labs/moosestack/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/514-labs/moosestack/copilot-instructions/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/514-labs/moosestack/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/514-labs/moosestack/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 519 This file is loaded in full into every session.

When invoked 519 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00519	$0.00519
Opus 5.5	$0.00208	$0.00208
Sonnet 5.5	$0.00104	$0.00104
Haiku 4.5	$0.00052	$0.00052

Measured 2mo ago against content hash d1f5521e9634, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

moosestack 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 2mo 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.

.github/copilot-instructions.md · 49 lines

How it starts

The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Moose Repository Guide

This is a monorepo containing the Moose project, built with Rust, TypeScript, and Python. The project utilizes PNPM and Turbo for JavaScript/TypeScript package management and Cargo for Rust components. Please follow these guidelines when contributing:

Code Standards

Required Before Each Commit

TypeScript/JavaScript: Run linting checks before submitting PRs
Rust: Run cargo clippy to ensure code passes Clippy's linting standards
Ensure all tests pass: cargo test for Rust components and appropriate test commands for TS/JS

Development Flow

Build TypeScript/JavaScript packages: pnpm build
Build Rust components: cargo build
Run tests:
- Rust: cargo test
- TypeScript/JavaScript: pnpm test
- End-to-end tests: ./apps/framework-cli-e2e and then pnpm test
Full CI check: Run appropriate build and test commands for affected packages

Repository Structure

apps/: Contains end-to-end tests for Moose, Moose the CLI, docs and some wrapper node packages for distribution
packages/: Common internal dependencies shared across the monorepo as well as moose libs in python and typescript
templates/: Standalone Moose templates that can be run in isolation
Rust components with their own Cargo.toml files
Configuration files for the monorepo:
- pnpm-workspace.yaml: Defines PNPM workspace
- turbo.json: Turbo Repo configuration
- Various Rust configuration files

Build System

JavaScript/TypeScript: PNPM workspaces with Turbo Repo for build orchestration
Rust: Cargo for managing Rust packages and dependencies
Cross-language: Commands to build the entire monorepo or specific components

Testing Strategy

Rust: Unit and integration tests using Cargo's testing framework
TypeScript/JavaScript: Unit tests for specific packages
End-to-end: Full integration tests in the apps directory

Key Guidelines

Follow the existing architecture and code organization
Respect language-specific best practices and idioms
Ensure cross-compatibility between components
Write tests for new functionality
Document public APIs and complex logic
When adding dependencies, ensure compatibility with the monorepo structure
For template modifications, verify they can still run in isolation

Read the full file on GitHub · 49 lines

Changes

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.

2mo ago First seen · 49 lines · 519 tokens per session scan A d1f5521e9634

Subscribe to this mod's changes

moosestack copilot-instructions.md is an instructions file published in the GitHub repository 514-labs/moosestack (591 stars, last pushed 3d ago), licensed MIT. It adds 519 tokens to every session, about $0.0021 per session on Opus 5.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-30.

data dataengineering deployment framework insights metrics

moosestack copilot-instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
moosestack copilot-instructions.md514-labs/moosestack	Instructions file	591	3d ago	MIT	A	519	GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

moosestack: Instructions file for GitHub Copilot