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/lesson-collection.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/lesson-collection)<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.
<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>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.00767 | $0.00767 |
| Opus 5.5 | $0.00307 | $0.00307 |
| Sonnet 5.5 | $0.00153 | $0.00153 |
| Haiku 4.5 | $0.00077 | $0.00077 |
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.
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_fixfindings - User rejects an artifact and requests revision (log what was wrong)
- Subagent returns
NEEDS_REVISIONverdict - 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-failureseverity:critical,high,medium,lowstatus:open,in-progress,resolved,wont-fix
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 · +6 lines · +85 tokens per session 053539707452
- 1mo ago Changed · +14 tokens per session 09be8b018698
- 1mo ago Changed · +5 lines · +100 tokens per session 2c33c1e38955
- 1mo ago First seen · 67 lines · 568 tokens per session scan A 74454ff36e2a
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.
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.