agentmods.dev

spec-kit-template platform.instructions.md

spec-kit-template platform.instructions.md is an instructions file for GitHub Copilot from lksnext-ai-lab/spec-kit-template. It costs 607 tokens per session, scanned A, original, Apache-2.0.

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.

In plain words
What is it for?
Use it when editing `.github` platform files, adding or changing agents, prompts, skills, commands, or related repository instructions.
Why use it?
Changes to agent and skill files can silently break names, paths, or expected interfaces. These rules keep the repository structure and existing contracts consistent.

Instructions file for GitHub Copilot

not rated 5 6mo ago A scan 607 tokens original Apache-2.0
View the source file lksnext-ai-lab/spec-kit-template
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/lksnext-ai-lab/spec-kit-template/platform
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.

agentmods badge for spec-kit-template platform.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/lksnext-ai-lab/spec-kit-template/platform.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.svg" alt="Measured on agentmods" 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. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00607 $0.00607
Opus 5 $0.00303 $0.00303
Sonnet 5 $0.00121 $0.00121
Haiku 4.5 $0.00061 $0.00061

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

  1. Rutas desde raíz (obligatorio)

    • En .github/** usar siempre rutas desde raíz del repo: docs/spec/...
    • Evitar enlaces relativos (../..) y rutas ambiguas

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

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

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

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

  6. Histórico

    • docs/spec/history/** debe estar excluido por defecto de procesos operativos (lint, plan, write, review).
    • Solo se toca al cerrar iteraciones.

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

  1. 5d 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 6mo ago), licensed Apache-2.0. It adds 607 tokens to every session, about $0.0030 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-31.

Building agents
Related

Other instructions, from other repositories

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,296 tokens

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.

openai/codex · 5,182 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

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

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,469 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens