agentmods.dev

spec-okf copilot-instructions.md

A set of project instructions that makes coding follow written specifications and a structured knowledge format. Spec-Driven Development means writing and agreeing on the requirements before implementing them.

In plain words
What is it for?
It helps developers plan features in numbered specification folders, check relevant project knowledge before coding, create missing specifications, and record lasting concepts in a shared knowledge log.
Why use it?
It reduces the risk of coding against unclear or missing requirements and keeps important project knowledge documented. Acceptance criteria in each specification define when work is complete.

Instructions file for GitHub Copilot

2 2mo ago A scan 188 tokens original MIT
View the source file giossaurus/spec-okf
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/giossaurus/spec-okf/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/giossaurus/spec-okf

Made for: GitHub Copilot.

Per session 188 This file is loaded in full into every session.
When invoked 188 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.00188 $0.00188
Opus 5 $0.00094 $0.00094
Sonnet 5 $0.00038 $0.00038
Haiku 4.5 $0.00019 $0.00019

Measured 2d ago against content hash 06a89fa4d0b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

templates/agents/copilot/.github/copilot-instructions.md · 17 lines

What it actually says

GitHub Copilot — Instruções

Este projeto usa Spec-Driven Development (SDD) + Open Knowledge Format (OKF).

A metodologia canônica está em methodology/sdd.md. Siga-a.

Regras:

  1. Antes de implementar, leia a spec relevante em specs/NNNN-nome/spec.md e o contexto em knowledge/. Se a spec não existir, crie-a antes de codar.
  2. Os critérios de aceitação da spec são a definição de pronto.
  3. Conhecimento durável vira conceito OKF em knowledge/concepts/ (campo type obrigatório) e ganha uma linha em knowledge/log.md.
  4. Use markdown estrutural; links entre conceitos são bundle-relativos (/...).

Mapa: methodology/sdd.md, docs/, specs/, knowledge/.

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. 2d ago First seen · 17 lines · 188 tokens per session scan A 06a89fa4d0b7

Subscribe to this mod's changes

spec-okf copilot-instructions.md is an instructions file published in the GitHub repository giossaurus/spec-okf (2 stars, last pushed 2mo ago), licensed MIT. It adds 188 tokens to every session, about $0.0009 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.

PlanningWriting and docs
Related

Other instructions, from other repositories

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

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

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,345 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

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.

vercel/next.js · 7,296 tokens