What is console copilot-instructions.md?

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.

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.

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.

console copilot-instructions.md — Instructions file by kubestellar

Install

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.

agentmods

npx agentmods add instructions/kubestellar/console/copilot-instructions

Clone the repo

git clone --depth 1 https://github.com/kubestellar/console

Made for: GitHub Copilot.

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. Scan, not verified.

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	$0.01166	$0.01166
Opus 5	$0.00583	$0.00583
Sonnet 5	$0.00233	$0.00233
Haiku 4.5	$0.00117	$0.00117

Measured 2d ago against content hash 4b151999849e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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

Make code changes
cd web && npm run build - MUST PASS
cd web && npm run lint - MUST PASS
git add .
git commit -m "message"
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.

2d 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 (130 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,166 tokens to every session, about $0.0058 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.

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.

github/spec-kit · 7,104 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 · 6,785 tokens

console copilot-instructions.md