apex-accelerator: Instructions file for GitHub Copilot

.github/instructions/lesson-collection.instructions.md

apex-accelerator lesson-collection.instructions.md is an instructions file for GitHub Copilot from jonathan-vella/apex-accelerator. It costs 767 tokens per session, scanned A, original, MIT.

A process for recording observations and lessons from workflow runs. It creates lessons-learned files when reviews fail, revisions are needed, validation breaks, or other defined problems occur.

In plain words
What is it for?
Use it in orchestrated coding workflows to record failed reviews, repeated steps, validation errors, deployment-policy issues, and user-raised concerns.
Why use it?
Important process problems can be forgotten after a workflow finishes. This preserves what went wrong so future runs can improve.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file. Also seen: mentions subagents.

This is jonathan-vella/apex-accelerator's own configuration. It tells GitHub Copilot how to work on apex-accelerator itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything apex-accelerator configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/jonathan-vella/apex-accelerator/main/.github/instructions/lesson-collection.instructions.md
Clone the repo
git clone --depth 1 https://github.com/jonathan-vella/apex-accelerator

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 apex-accelerator lesson-collection.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/lesson-collection/github.svg)](https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/lesson-collection)
Your own site
<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/lesson-collection"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/lesson-collection/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.

agentmods 80×15 button for apex-accelerator lesson-collection.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/jonathan-vella/apex-accelerator/lesson-collection"><img src="https://agentmods.dev/badge/instructions/jonathan-vella/apex-accelerator/lesson-collection.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 767 This file is loaded in full into every session.
When invoked 767 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00767 $0.00767
Opus 5.5 $0.00307 $0.00307
Sonnet 5.5 $0.00153 $0.00153
Haiku 4.5 $0.00077 $0.00077

Measured 6d ago against content hash 053539707452, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

apex-accelerator lesson-collection.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.

.github/instructions/lesson-collection.instructions.md · 78 lines

How it starts

The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Lesson Collection Protocol

Orchestrators collect process observations during workflow execution and generate 09-lessons-learned.json + 09-lessons-learned.md as workflow completion artifacts (same pattern as 00-handoff.md and 00-session-state.json).

Initialization

Session state follows the apex-recall rules in copilot-instructions.md (init for new projects, show on resume); never read or edit 00-session-state.json directly. On resume, preserve existing lesson entries. Initialize with apex-recall init <project> --json. Create 09-lessons-learned.json with file-editing tools only when absent:

{
  "workflow_mode": "production",
  "project": "{project}",
  "lessons": []
}

New workflow logs use "production". The schema's historical "e2e" value and existing lesson artifacts remain valid compatibility evidence; do not rewrite them or infer a runnable E2E workflow from that retained value.

The CLI has no apex-recall lessons subcommand. Append schema-compliant entries to the lesson artifact with file-editing tools; session findings are not a replacement for the structured lesson log. Register the artifact through recall:

apex-recall checkpoint <project> <step> lessons \
   --artifact agent-output/<project>/09-lessons-learned.json --json

When to Record a Lesson

Production Orchestrator Triggers

  • Challenger review returns must_fix findings
  • User rejects an artifact and requests revision (log what was wrong)
  • Subagent returns NEEDS_REVISION verdict
  • Deployment what-if reveals Azure Policy violations
  • User explicitly flags an issue or concern during approval

Lesson Schema

Formal JSON Schema: tools/schemas/lesson-log.schema.json. Required fields per entry: id, step, category, severity, title, observation, root_cause, recommendation, applies_to, applies_to_paths, status. Allowed enums:

  • category: agent-behavior, skill-gap, prompt-quality, validation-gap, workflow-design, context-budget, artifact-quality, factual-accuracy, deployment-failure
  • severity: critical, high, medium, low
  • status: open, in-progress, resolved, wont-fix

Read the full file on GitHub · 78 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. 6d ago Changed · +6 lines · +85 tokens per session 053539707452
  2. 1mo ago Changed · +14 tokens per session 09be8b018698
  3. 1mo ago Changed · +5 lines · +100 tokens per session 2c33c1e38955
  4. 1mo ago First seen · 67 lines · 568 tokens per session scan A 74454ff36e2a

Subscribe to this mod's changes

apex-accelerator lesson-collection.instructions.md is an instructions file published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 767 tokens to every session, about $0.0031 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.

Related

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

microsoft/vscode · 9,715 tokens

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,786 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

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

microsoft/vscode · 2,731 tokens

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.

denoland/deno · 3,077 tokens