Borrowing it
Nothing to install: this file belongs to jonathan-vella/apex-accelerator. 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/jonathan-vella/apex-accelerator/main/.github/instructions/code-quality.instructions.mdgit clone --depth 1 https://github.com/jonathan-vella/apex-acceleratorWrote 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/jonathan-vella/apex-accelerator/code-quality)<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/code-quality"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/code-quality/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.
<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/code-quality"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/code-quality.svg" alt="Reviewed on agentmods" width="80" 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.00827 | $0.00827 |
| Opus 5.5 | $0.00331 | $0.00331 |
| Sonnet 5.5 | $0.00165 | $0.00165 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
apex-accelerator code-quality.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 6d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Quality Instructions
Language-Specific Precedence
Language-specific instruction files take precedence over these general guidelines. In particular:
- PowerShell (
powershell.instructions.md): always include comment-based help (.SYNOPSIS,.DESCRIPTION,.EXAMPLE). - Bicep (
iac-bicep-best-practices.instructions.md): always use@descriptionannotations on parameters, variables, and outputs. - Shell (
shell.instructions.md): include a header comment explaining the script's purpose.
These requirements are additive — public-facing APIs and parameters must be documented per their language rules, while internal code follows the minimal-comment philosophy below.
Commenting: Core Principle
Write code that speaks for itself. Comment only when necessary to explain WHY, not WHAT.
AVOID These Comments
- Obvious:
let counter = 0; // Initialize counter to zero - Redundant: comment repeats what the code already says
- Outdated: comment doesn't match the code
WRITE These Comments
- Complex business logic: explains WHY a specific calculation
- Non-obvious algorithms: explains the algorithm choice
- Regex patterns: explains what the regex matches
- API constraints or gotchas: explains external limitations
Decision Framework
- Is the code self-explanatory? → No comment needed
- Would a better name eliminate the need? → Refactor instead
- Does this explain WHY, not WHAT? → Good comment
- Will this help future maintainers? → Good comment
Annotations
Use standard annotation tags: TODO, FIXME, HACK, NOTE,
WARNING, PERF, SECURITY, BUG, REFACTOR, DEPRECATED.
Anti-Patterns
- Dead code left as comments — delete it (Git has history)
- Journal comments tracking changes — use Git log
- Closing brace comments — refactor into smaller functions
- Commented-out code blocks — delete or explain why kept
Code Review Priorities
🔴 CRITICAL (Block merge): Security vulns, logic errors, breaking changes, data loss
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.
- 6d ago Changed · +7 tokens per session d9fd43d7266d
- 1mo ago Changed · -12 lines · -114 tokens per session 02bb11577a2c
- 1mo ago Changed · -9 tokens per session 5223713c1f41
- 1mo ago First seen · 109 lines · 943 tokens per session scan A e1dcd1935f2f
apex-accelerator code-quality.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 827 tokens to every session, about $0.0033 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-30.
Other instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.