What is spec-kit-template platform.instructions.md?

A set of repository instructions for maintaining platform files such as agents, prompts, skills, workflows, and other instructions. It defines naming, file-location, editing, and compatibility rules for those files.

Use it when editing `.github` platform files, adding or changing agents, prompts, skills, commands, or related repository instructions.

Changes to agent and skill files can silently break names, paths, or expected interfaces. These rules keep the repository structure and existing contracts consistent.

How lksnext-ai-lab/spec-kit-template configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to lksnext-ai-lab/spec-kit-template. 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/lksnext-ai-lab/spec-kit-template/main/.github/instructions/platform.instructions.md

Clone the repo

git clone --depth 1 https://github.com/lksnext-ai-lab/spec-kit-template

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/lksnext-ai-lab/spec-kit-template/platform/github.svg)](https://agentmods.dev/instructions/lksnext-ai-lab/spec-kit-template/platform)

Your own site

<a href="https://agentmods.dev/instructions/lksnext-ai-lab/spec-kit-template/platform"><img src="https://agentmods.dev/badge/instructions/lksnext-ai-lab/spec-kit-template/platform/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/lksnext-ai-lab/spec-kit-template/platform"><img src="https://agentmods.dev/badge/instructions/lksnext-ai-lab/spec-kit-template/platform.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 607 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.00607	$0.00607
Opus 5.5	$0.00243	$0.00243
Sonnet 5.5	$0.00121	$0.00121
Haiku 4.5	$0.00061	$0.00061

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

Security

Grade A, and why

spec-kit-template platform.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/instructions/platform.instructions.md · 60 lines

How it starts

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

Platform instructions (.github/**)

Estas instrucciones aplican a la “plataforma” del repo: agentes, prompts, skills, workflows e instrucciones.

Reglas duras

Rutas desde raíz (obligatorio)
- En .github/** usar siempre rutas desde raíz del repo: docs/spec/...
- Evitar enlaces relativos (../..) y rutas ambiguas
No romper contratos
- Si un archivo define un comando, un agente o un skill, mantener su interfaz estable:
  - nombres de comandos (/new-spec, /plan-iteration, etc.)
  - nombres de agentes (spc-...)
  - estructura y propósito de cada skill
- Si hay que renombrar/migrar, hacerlo completo:
  - actualizar referencias en docs/kit y en .github/**
  - y dejar el repo coherente (sin restos)
Cambios mínimos, intención clara
- Evitar “refactors” cosméticos
- Cambiar solo lo necesario por coherencia, claridad o corrección
- Mantener el lenguaje operativo (qué hace / entradas / salidas / archivos)
Convenciones de naming y formato
- Agents: .github/agents/spc-<fase>-<rol>.agent.md
- Prompts: .github/prompts/*.prompt.md
- Skills: .github/skills/<skill>/SKILL.md (carpeta + SKILL.md)
- Instructions: .github/copilot-instructions.md y .github/instructions/*.instructions.md
Separación SPEC vs IMP
- SPEC plan usa Pxx en docs/spec/01-plan.md
- Implementación usa Txx en docs/spec/spc-imp-*
- No mezclar IDs en los artefactos equivocados
Histórico
- docs/spec/history/** debe estar excluido por defecto de procesos operativos (lint, plan, write, review).
- Solo se toca al cerrar iteraciones.
No inventar
- No afirmar que existe un archivo/comando/agente si no existe en el repo.
- Si falta algo: proponerlo como cambio explícito o registrar TODO en SPEC.

Edición de agentes y prompts

Mantener entradas y salidas claras.
Incluir rutas de archivos explícitas en “Outputs”.
Evitar instrucciones contradictorias entre prompts/agentes.
Los prompt files deben ser ejecutables y reproducibles (procedimiento consistente).

Read the full file on GitHub · 60 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 · 60 lines · 607 tokens per session scan A f009168d2cb1

Subscribe to this mod's changes

spec-kit-template platform.instructions.md is an instructions file published in the GitHub repository lksnext-ai-lab/spec-kit-template (5 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 607 tokens to every session, about $0.0024 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-31.

Building agents

spec-kit-template platform.instructions.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
spec-kit-template platform.instructions.mdlksnext-ai-lab/spec-kit-template	Instructions file	5	8mo ago	Apache-2.0	A	607	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	yesterday	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

spec-kit-template: Instructions file for GitHub Copilot