console: Instructions file for GitHub Copilot

.github/copilot-instructions.md

console copilot-instructions.md is an instructions file for GitHub Copilot from kubestellar/console. It costs 1,166 tokens per session, scanned A, original, Apache-2.0.

A set of coding rules for the KubeStellar Console project, whose frontend uses React and TypeScript and whose backend uses Go. It defines the required build, lint, commit, and pull-request steps.

In plain words
What is it for?
Use it when changing the console code, especially when building or linting the frontend, checking TypeScript code, preparing commits, or opening pull requests linked to issues.
Why use it?
It gives a coding agent clear project-specific checks and standards to follow before code is committed. This helps catch failed builds, lint errors, missing imports, and incomplete pull requests.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is kubestellar/console's own configuration. It tells GitHub Copilot how to work on console itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything console configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kubestellar/console. 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/kubestellar/console/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/kubestellar/console

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.

agentmods badge for console copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/kubestellar/console/copilot-instructions/github.svg)](https://agentmods.dev/instructions/kubestellar/console/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/kubestellar/console/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kubestellar/console/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.

agentmods 80×15 button for console copilot-instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/kubestellar/console/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/kubestellar/console/copilot-instructions.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,166 This file is loaded in full into every session.
When invoked 1,166 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01166 $0.01166
Opus 5.5 $0.00466 $0.00466
Sonnet 5.5 $0.00233 $0.00233
Haiku 4.5 $0.00117 $0.00117

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

Security

Grade A, and why

console 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 1mo 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 · 161 lines

How it starts

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

Copilot Instructions for KubeStellar Console

MANDATORY: Build and Lint Before Every Commit

YOU MUST RUN THESE COMMANDS BEFORE EVERY SINGLE COMMIT:

cd web
npm run build
npm run lint

IF BUILD FAILS → FIX IT → RUN AGAIN IF LINT FAILS → FIX IT → RUN AGAIN ONLY COMMIT AFTER BOTH PASS

DO NOT PUSH CODE THAT FAILS BUILD OR LINT. This is non-negotiable.

Commit Workflow

  1. Make code changes
  2. cd web && npm run build - MUST PASS
  3. cd web && npm run lint - MUST PASS
  4. git add .
  5. git commit -m "message"
  6. Push

Project Structure

  • Frontend: React + TypeScript in /web/
  • Backend: Go in root directory
  • Build: npm run build in web directory
  • Lint: npm run lint in web directory

Code Standards

TypeScript

  • Use explicit types (no any)
  • Functional components with hooks
  • Verify imports exist before using them

Before Using a Function

  • Search the codebase to verify it exists
  • Check the correct import path
  • Never call undefined functions

PR Requirements

MANDATORY: Link PR to Issue

The FIRST LINE of every PR body MUST be Fixes #ISSUE_NUMBER where ISSUE_NUMBER is the issue you were assigned to fix. This is required so GitHub automatically closes the issue when the PR is merged.

Example — if you are fixing issue #3400, the PR body must start with:

Fixes #3400

Do NOT omit this. Do NOT put it at the end. It MUST be the first line.

  • All commits must pass build and lint
  • Keep changes focused on the issue

Commit Conventions

Emoji Prefixes

Emoji Type When
✨ Feature New functionality
🐛 Bug fix Fixing broken behavior
📖 Docs Documentation only
📝 Proposal Design proposals
⚠️ Breaking change API or behavior changes
🌱 Other Tests, CI, refactoring, tooling

DCO Sign-off (Required)

All commits MUST be signed off for DCO compliance:

git commit -s -m "✨ Short descriptive message"

Read the full file on GitHub · 161 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.

  1. 1mo ago First seen · 161 lines · 1,166 tokens per session scan A 4b151999849e

Subscribe to this mod's changes

console copilot-instructions.md is an instructions file published in the GitHub repository kubestellar/console (148 stars, last pushed today), licensed Apache-2.0. It adds 1,166 tokens to every session, about $0.0047 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.

Related

Other instructions, from other repositories

create-trimble-app typescript.instructions.md

Instructions for julianoczkowski/create-trimble-app, covering typescript patterns for modus components, event type casting, common event types, component ref types and modal ref pattern.

julianoczkowski/create-trimble-app · 583 tokens

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

microsoft/vscode · 9,649 tokens

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.

vercel/next.js · 7,384 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens