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/514-labs/moosestack/copilot-instructionsgit clone --depth 1 https://github.com/514-labs/moosestackWrote 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/514-labs/moosestack/copilot-instructions)<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="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.00519 | $0.00519 |
| Opus 5 | $0.00260 | $0.00260 |
| Sonnet 5 | $0.00104 | $0.00104 |
| Haiku 4.5 | $0.00052 | $0.00052 |
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 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 — 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 clippyto ensure code passes Clippy's linting standards - Ensure all tests pass:
cargo testfor 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
- Rust:
- 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 distributionpackages/: Common internal dependencies shared across the monorepo as well as moose libs in python and typescripttemplates/: 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 workspaceturbo.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
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 · 49 lines · 519 tokens per session scan A d1f5521e9634
moosestack copilot-instructions.md is an instructions file published in the GitHub repository 514-labs/moosestack (588 stars, last pushed 1mo ago), licensed MIT. It adds 519 tokens to every session, about $0.0026 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-30.
Other instructions, from other repositories
arandu CLAUDE.md
Instructions for vdittgen/arandu, covering arandu, architecture, top-level packages, commands and coding standards.
jesse AGENTS.md
AGENTS.md instructions for jesse-ai/jesse, covering jesse repository guide for ai agents, skills, key characteristics, central framework and technology stack.
AgentEval copilot-instructions.md
Copilot instructions for AgentEvalHQ/AgentEval, covering agenteval - ai coding agent instructions, architecture overview, environment setup, optional: secondary models for comparison and build & test commands.
LarAgent AGENTS.md
Instructions for MaestroError/LarAgent, covering purpose, key principles, planning, executing plan and testing.
mcp-ssh-manager CLAUDE.md
Claude Code instructions for bvisible/mcp-ssh-manager, covering claude.md, project overview, architecture, commands and setup and installation.
zhin zhin-plugin.instructions.md
Instructions for zhinjs/zhin, covering zhin plugin runtime authoring, package contract, convention directories, imports and native typescript and command routes.