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/holger1411/astrodeck/copilot-instructionsgit clone --depth 1 https://github.com/holger1411/astrodeckWhat 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.02534 | $0.02534 |
| Opus 5 | $0.01267 | $0.01267 |
| Sonnet 5 | $0.00507 | $0.00507 |
| Haiku 4.5 | $0.00253 | $0.00253 |
Grade A, and why
astrodeck 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 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Copilot Instructions — AstroDeck
Project Overview
AstroDeck is an open-source component library and starter kit for building Astro.js websites. It provides pre-built, production-ready sections for landing pages and SaaS websites.
Always check PROJECT.md first for project-specific overrides, then follow the conventions in this file.
Tech Stack
| Layer | Technology | Version |
|---|---|---|
| Framework | Astro | v6.x |
| Styling | Tailwind CSS | v4.x |
| Tailwind Integration | @tailwindcss/vite | (Vite plugin, NOT @astrojs/tailwind) |
| UI Components | shadcn/ui + Radix UI | React |
| Type Safety | TypeScript | strict mode |
Critical: Tailwind CSS v4 is configured via the @tailwindcss/vite Vite plugin. Never suggest @astrojs/tailwind (v3 only) or tailwind.config.js.
Project Structure
src/
components/
sections/ # Page sections: Hero.astro, CTA.astro, Pricing.astro, FAQ.astro, etc.
ui/ # shadcn/ui React components: button.tsx, card.tsx, etc.
layouts/ # BaseLayout.astro, FullWidthLayout.astro, MinimalLayout.astro,
# AuthLayout.astro, ArticleLayout.astro
pages/ # File-based routing — index.astro maps to /
content/ # Astro Content Collections (blog posts)
styles/
globals.css # All design tokens + Tailwind v4 @theme block — customize colors here
lib/
utils.ts # cn() helper and utilities
public/ # Static assets (fonts, favicon, images)
astro.config.mjs # Astro + Vite configuration
Code Style Rules
Imports
Always use the @/ path alias for imports from src/. Never use relative paths.
// Correct
import Hero from "@/components/sections/Hero.astro";
import { Button } from "@/components/ui/button";
import BaseLayout from "@/layouts/BaseLayout.astro";
// Wrong
import Hero from "../components/sections/Hero.astro";
Colors and Styling
Use CSS variable-based Tailwind classes. Never hardcode colors or use inline styles.
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 · 349 lines · 2,534 tokens per session scan A f69a0d8bcd96
astrodeck copilot-instructions.md is an instructions file published in the GitHub repository holger1411/astrodeck (72 stars, last pushed 26d ago), licensed MIT. It adds 2,534 tokens to every session, about $0.0127 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
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.