What is apex-accelerator json.instructions.md?

Formatting and organization rules for JSON and JSONC configuration files. JSONC is JSON that also permits comments.

It guides indentation, line endings, key order, comments in JSONC files, and the layout of common project configuration and governance files.

It reduces inconsistent formatting and invalid JSON caused by features such as trailing commas, while keeping configuration easy to review.

apex-accelerator json.instructions.md — Instructions file by jonathan-vella

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/jonathan-vella/apex-accelerator/json

Clone the repo

git clone --depth 1 https://github.com/jonathan-vella/apex-accelerator

Made for: GitHub Copilot.

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

When invoked 385 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.00385	$0.00385
Opus 5	$0.00192	$0.00192
Sonnet 5	$0.00077	$0.00077
Haiku 4.5	$0.00038	$0.00038

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

Security

Grade A, and why

apex-accelerator 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 3d 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/json.instructions.md · 45 lines

What it actually says

JSON Guidelines

Instructions for writing consistent JSON and JSONC files in this repository.

Formatting

Formatter: Prettier (configured in devcontainer)
Indentation: 2 spaces
Trailing commas: not allowed in .json files (invalid JSON)
Line endings: LF (\n) — enforced by .editorconfig / VS Code settings
Final newline: always include a trailing newline

JSONC (JSON with Comments)

Files like .vscode/mcp.json, devcontainer.json, and .markdownlint-cli2.jsonc use JSONC format:

Use // for single-line comments explaining non-obvious configuration
Group related settings with section comments
Do not use /* */ block comments

Key Ordering

For configuration files, follow a logical grouping:

package.json: name, version, description, private, scripts, devDependencies, repository, keywords, author, license
mcp.json: group servers by type (HTTP first, then stdio)
devcontainer.json: name, image, features, lifecycle commands, containerEnv, customizations, mounts, remoteUser

Governance Constraint Files

Files like 04-governance-constraints.json in agent-output/ are generated by the azure-governance-discovery skill's discover.py. See .github/instructions/references/governance-discovery-reference.md for the full JSON schema and required fields.

Do not manually edit — regenerate via the governance discovery workflow

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.

3d ago First seen · 45 lines · 385 tokens per session scan A 7ad4662e52ad

Subscribe to this mod's changes

apex-accelerator json.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed 6d ago), licensed MIT. It adds 385 tokens to every session, about $0.0019 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.

agentic-ai azure bicep copilot github-copilot iac

claude-code-settings copilot-instructions.md

Instructions for feiskyer/claude-code-settings, covering claude.md, environment setup, required dependencies, configuration and skills.

feiskyer/claude-code-settings · 649 tokens

squad copilot-instructions.md

Copilot instructions for bradygaster/squad, covering copilot coding agent — squad instructions, ⚠️ identity lock — read this first, 🚦 route before you act — generic copilot sessions, adversarial input handling and team context.

bradygaster/squad · 1,349 tokens

vscode-unify-chat-provider AGENTS.md

Instructions for smallmain/vscode-unify-chat-provider, a project described as: Integrate multiple LLM API providers into VS Code's GitHub Copilot Chat using the Language Model API. One-click use of your Claude Code, Gemini CLI, Antigravity, Github Copilot, OpenAI Codex (ChatGPT Plus/Pro), xAI Grok (SuperGrok / X…

smallmain/vscode-unify-chat-provider · 271 tokens

apex-accelerator json.instructions.md