Borrowing it
Nothing to install: this file belongs to franklesniak/copilot-repo-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.
curl -O https://raw.githubusercontent.com/franklesniak/copilot-repo-template/main/.github/instructions/json.instructions.mdgit clone --depth 1 https://github.com/franklesniak/copilot-repo-templateWrote 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.
[](https://agentmods.dev/instructions/franklesniak/copilot-repo-template/json)<a href="https://agentmods.dev/instructions/franklesniak/copilot-repo-template/json"><img src="https://agentmods.dev/badge/instructions/franklesniak/copilot-repo-template/json.svg" alt="Measured on agentmods" height="20"></a>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.04188 | $0.04188 |
| Opus 5 | $0.02094 | $0.02094 |
| Sonnet 5 | $0.00838 | $0.00838 |
| Haiku 4.5 | $0.00419 | $0.00419 |
Grade A, and why
copilot-repo-template json.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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JSON Writing Style
Version: 1.4.20260629.0
Metadata
- Status: Active
- Owner: Repository Maintainers
- Last Updated: 2026-06-29
- Scope: Defines authoring standards for JSON and JSONC files in this repository, including configuration, schemas, fixtures, generated metadata, and machine-readable contracts. Covers dialect policy, formatting, key ordering, naming, data modeling, schema usage, comments, security, and generated output.
- Related: Repository Copilot Instructions,
.gitattributesRules, YAML Writing Style (companion guide, if present)
Purpose and Scope
This guide establishes how JSON and JSONC files are authored in this repository. JSON is treated as a machine-readable contract: it MUST be unambiguous, deterministic, and safe to consume by tools and downstream automation.
The guide applies to every .json and .jsonc file in the repository, including configuration, schemas, fixtures, examples, policy documents, generated metadata, and any other JSON-shaped artifact, regardless of programming language or surrounding stack.
Note: This document uses RFC 2119 keywords (MUST, MUST NOT, SHOULD, SHOULD NOT, MAY) to indicate requirement levels.
Line-ending pinning, BOM behavior, end-of-file newline, and trailing whitespace policy for JSON files are governed by .gitattributes Rules; this guide does not duplicate or override those rules.
Quick Reference Checklist
- [All]
.jsonfiles MUST be strict JSON;.jsoncMAY be used only when the consuming tool explicitly supports JSONC. - [All] MUST use 2-space indentation; MUST NOT use tabs.
- [All] MUST NOT include trailing commas in strict JSON.
- [All] Keys and string values MUST be double-quoted.
- [All] MUST NOT blindly sort keys; MUST preserve intentional grouping and tool-managed ordering (for example,
package.json, JSON/JSONC lockfiles, and other generated files). - [All] Strict JSON MUST NOT contain comments.
- [All] Production or load-bearing JSON files MUST have schema validation; durable fixtures, examples, policy documents, and config contracts SHOULD have schema validation.
- [All] MUST NOT commit secrets; example values MUST be obviously fake.
- [All] Untrusted JSON MUST be validated before use and MUST NOT be evaluated as executable code.
- [All] Generated JSON MUST be reproducible and SHOULD identify its source or generation command.
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.
- 8d ago First seen · 167 lines · 4,188 tokens per session scan A e6a6ff13749c
copilot-repo-template json.instructions.md is an instructions file published in the GitHub repository franklesniak/copilot-repo-template (8 stars, last pushed 22d ago), licensed MIT. It adds 4,188 tokens to every session, about $0.0209 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.
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.
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.
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).
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).
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.
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.